Plugins and secrets

Plugins let Para work in other services with a credential you connect. Install case.dev for named projects, connect a service from the catalog, or save an API key as a secret for a tool the catalog does not cover. Each Para has its own plugins and secrets: yours are on Plugins, and the Shared Para’s are on Shared Para.

Install case.dev for projects

Every Para has Desk and Personal for documents. To add named projects, open Plugins and choose Install beside case.dev. No case.dev account or API key is needed. This installs it for your own Para, not the whole organization. Your existing Desk and Personal documents stay available.

For the Shared Para, an organization owner or administrator installs case.dev separately on Shared Para. A colleague’s installation does not enable projects for your Para. Project access still follows your organization’s access groups.

What you can connect

The catalog on Plugins is grouped by category. Each row shows what Para can do with it, such as Read and Write, and links to the provider’s API reference.

Your organization’s document systems, such as Google Drive and Microsoft 365, are listed under Document systems on the same page. See Document connections.

Connect a service

1. 1

   Open Plugins

   Go to Plugins and find the service. The row shows how it connects: a provider sign-in, an API key or token, or a client ID and secret.

2. 2

   Authorize your account

   Select Connect, then complete the provider sign-in or enter the requested credentials. Follow the provider-specific instructions in the form. Some services run through the provider’s own MCP server; you still only enter a key, not a server address.

3. 3

   Try a first task

   Ask Para to read a specific issue or account you already have access to. Confirm it retrieved the intended record before asking for changes.

Whose credential Para uses

A plugin on your own Para uses your account and the access you have in that service. Other members connect their own accounts. A plugin on the Shared Para is connected by an owner or administrator, and everyone who can mention the Shared Para acts with that credential, so use a service account or organization credential with the access you intend to share. Members can see which plugins the Shared Para has, but not their credentials.

Secrets for other tools

When a service has no plugin, save its API key under Secrets on Plugins, then ask Para to use it, for example to run that service’s command-line tool. Each secret has a name in capital letters, digits, and underscores, such as ACME_API_KEY, and a value. Names Para reserves for its own configuration are refused.

• Each Para can hold up to 25 secrets. Every assignment on that Para can use all of them; naming one in a request is guidance, not an access restriction.
• Values cannot be viewed after saving. Replace or remove a secret from the same list.
• Secrets on your Plugins page are for your own Para. The Shared Para has its own, managed by owners and administrators on Shared Para.
• Enter keys in the Secrets form, not in a chat message. Para cannot save a secret from conversation.

Plugins, MCP, and workflows

• Plugins let Para use another service. Para’s MCP server does the reverse: it lets another assistant delegate to Para. You cannot add your own MCP server address to Para; use a catalog plugin or a secret.
• A skill or marketplace workflow supplies instructions; it does not authorize a service account.
• Expired, revoked, or insufficient provider permissions can prevent a task even when Para itself is working. Reconnect or correct permissions from the provider.
• If a provider sign-in says the service is not configured for Para yet, CaseMark has not enabled that sign-in. Contact support.

• Shared ParaPlugins and secrets everyone in a Slack channel can use.
• AI assistants through MCPConnect another assistant to Para.
• Integration overviewChoose the appropriate kind of connection.