Choose where to work
| Surface | How you use it | Files and limits |
|---|---|---|
| Send work to your own Para address, or to the Shared Para at the organization’s para@ address; continue by replying to the thread. | Incoming attachments and supported reply attachments; email is not end-to-end encrypted. | |
| Slack | Direct-message the Para app after installation and personal linking. Mention it in a channel to reach the Shared Para. | Send files in the DM; finished files arrive as uploads. Channel conversations are visible to the whole organization. |
| Microsoft Teams | Talk to Para in a personal app chat. | Send attachments; accept each outbound file card to upload it to your OneDrive. Teams channels are not supported yet. |
| Microsoft Copilot: direct Para | Your existing Para replies in the Copilot conversation. | Text-only. Can use existing project documents. Available for testing; not yet generally available. |
| MCP: another AI assistant | Claude, ChatGPT, Codex, or a compatible Copilot agent delegates to Para. | The other assistant does not automatically share its files or conversation. Results go to the selected connected channel. |
| Work page | Write to Para in the browser and continue the conversation there. | Attach up to 10 files totaling 20 MB, or name documents already in Projects. |
- EmailAddress, threads, attachments, and delivery.
- SlackApp installation, personal linking, and files.
- Shared ParaThe organization’s Para in Slack and Teams channels, and what it can use.
- Microsoft TeamsMicrosoft administrator approval, app installation, and OneDrive file cards.
- Microsoft CopilotDirect Para versus MCP, setup, and text-only limits.
- AI assistants through MCPConnection, authorization, delegation, and results.
- Work pageAssignments and follow-ups in the browser.
Document sources and tools
A document connection gives Para access to a source system; it is not another chat channel. A plugin lets Para use another service with the credential you connect, and a secret gives it an API key for anything a plugin does not cover. A skill or marketplace workflow gives Para reusable instructions.
- Document connectionsDrive, Microsoft 365, other document systems, and availability.
- PluginsConnect services such as Linear, GitHub, or Salesforce, and save API keys.
- MeetingsRecording, transcripts, access, and provider limitations.
- AutomationsScheduled work and delivery destinations.
The same document rules everywhere
Incoming documents land on your Desk. Without the case.dev plugin, Para keeps documents in Desk and Personal. With it, Para files documents in the project they concern, creates a clearly new project, and asks when several projects are plausible. ZIPs are stored intact. Storing a format does not guarantee that its contents can be analyzed.
For incoming messages, send at most 10 files: up to 20 MB in total by email, or 1 GB in Slack and Teams. For larger files, upload through Projects and name the files in your request. Creating named projects requires the case.dev plugin on your Para. These are Para intake limits; your provider may impose additional restrictions.
Connections and permissions
Slack and Teams require both an organization connection and your personal identity link. An AI assistant connection uses your Para organization when you sign in. Connecting another app does not grant access to another person’s private projects. Anything shared with the Shared Para is available to everyone in the organization.
Availability
Channels lists where you can reach Para: the Work page, email, Slack, Teams, AI assistants, and meetings. Plugins lists the services, document systems, and secrets Para can use. Direct Para in Copilot and the Copilot MCP app are available for testing, but are not yet generally available. Connections marked “Coming soon” or “Not enabled” cannot be used yet.