Microsoft Teams

Set up Teams

1. 1

   Connect your organization

   Open Channels, choose Microsoft Teams, and follow the setup dialog. A Microsoft administrator approves the organization connection. You also need to install the Para app in Teams.

2. 2

   Install the Para app

   Install the Para app supplied for your organization. For a custom app package, use Teams → Apps → Manage your apps → Upload an app → Upload a custom app, or have your administrator distribute it. The ZIP contains the app’s configuration and icons; Para continues to run on its servers.

3. 3

   Link your personal Microsoft account

   Complete the personal account connection in Para’s Teams setup. Use your account from the connected Microsoft organization so Para can recognize you.

4. 4

   Send a personal chat message

   Open Para’s personal app chat and ask for a brief reply. If you are testing a preview, use the app supplied for that preview.

Receive files from Para

1. 1

   Request the output

   Ask for the formats you need, such as PDF, Word, Excel, or ZIP. Para saves the work to document storage before preparing delivery: Desk or Personal without case.dev, or the relevant project with the plugin.

2. 2

   Allow each file

   Teams displays a card asking permission to upload a file to your OneDrive. Select Allow for each file you want. Decline means that file will not be uploaded.

3. 3

   Open the completed file card

   Wait for the resulting file card and open it. The file becomes available after you allow the upload and the completed file card appears.

Send a document to Para

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.

Current limitations

• A personal chat reaches your own Para. @mentioning Para in a team channel or group chat reaches the organization’s Shared Para instead, and everyone in the organization can see that work.
• Microsoft 365 Copilot is a separate, text-only way to use Para; use Teams to exchange files with Para.
• Teams file delivery requires the recipient’s consent and an available OneDrive destination. Some deliverables may arrive as download links that require Para sign-in when they cannot be attached.

If something does not work

• Cannot attach a file: confirm you are in Para’s personal chat and have the current app package provided by your administrator. Ask your administrator to check app policy if uploading a package is unavailable.
• “This card action is not supported”: verify the current app version and try a newly generated card after the update. Restarting Teams alone will not fix this error. If a fresh card still fails, contact support with the time and filename.
• Para does not recognize you: finish your personal Microsoft identity link on Channels. The Teams setup screen shows the linked account and Microsoft organization.
• Open in Teams does not reach Para: reopen the launcher and choose Use the web app instead, then open Para’s chat from there.
• Allow does not produce an openable file: check the current run and report the failed card. Do not treat the consent request as a completed upload.

• Para in Microsoft CopilotTwo Copilot modes and their file limitations.
• Compare all integrationsChoose an integration and review shared access rules.