Available connections
| Connection | Source | Availability |
|---|---|---|
| Google Drive | My Drive and Shared Drives | Available when enabled to your organization; otherwise the row shows Not enabled. |
| Microsoft 365 | OneDrive for Business and SharePoint | Connect from Plugins; your Microsoft permissions and organization’s policies apply. |
| Other document systems | Systems added by the case.dev plugin | Listed under Document systems once case.dev is installed on your Para. |
Connect a document account
Find the provider
Open Plugins and find the provider under Document systems. Use Connect or Add account. Wait for the document connection list to finish loading.
Authorize the source account
Sign in to the intended provider account and review its consent. If your organization requires administrator approval, complete that before continuing.
Check the connected account
Return to Plugins and confirm the account shown. Connecting a document account is separate from connecting Slack, Teams, or an MCP client.
Give Para a specific brief
Name the source, project, and documents to use. Confirm any project selection Para asks you to make before analysis.
What a connection does not mean
- Connecting an account does not automatically add every document to Para. Tell Para which documents to use and confirm the project where they should be filed.
- Provider account permissions and Para project permissions still apply. Connecting a system does not make its files public to your organization.
- Microsoft document access is distinct from the Teams chat connection and the Copilot MCP authorization. One does not complete the others.
- Disconnecting an account is not a request to delete documents already filed in a project. Manage those documents in Projects.
If a document is missing
Confirm the account and source location, your access in the provider, and the destination project. Reauthorize if the provider grant was revoked. If the connector is not enabled, upload the document directly to Projects instead.