# Connections

A connection authorizes Playbooks to use an external account through a supported integration or provider. It records the account relationship; the consuming resource still needs the appropriate assignment and current permission to use it.

For example, connecting a document service can make an account available for authorized work. It does not mean every Agent, Project, or Site may use that account.

## Authorize and assign

1. Choose the connector for the operation you need.
2. Confirm the external account and destination Workspace.
3. Complete the provider's supported authorization flow.
4. Review the permitted operations and receiving resource.
5. Assign access where required and verify a small task.

| Consumer | Access model |
| --- | --- |
| Agent | Explicit authorized assignment |
| Chat | Eligible Workspace access under the current person's authority |
| Project | Development assignment |
| Site | Independently authorized production assignment |

Connecting an account and selecting it as a service provider are also different actions. Review the actual configuration before assuming a connection replaced a managed capability.

## Connect from the Composer

Use `/connector` in the [slash command menu](/docs/composer/slash-commands) to enter the available setup flow. Confirm the provider account and receiving context shown there. If you finish account authorization but leave before assignment is complete, the Workspace account may be connected while the intended resource still cannot use it.

When setup offers several accounts, select the one that contains the intended data. Similar account names do not establish the same organization, permissions, or billing relationship.

After setup, use a small request to verify the path:

> Read the specified record from this account and summarize its current status. Include a link to the original record.

Choose an operation the Connector actually supports. A successful read establishes that read path; it does not establish permission to send messages, edit records, or use another account.

## Example: give a specialist focused access

A research Agent may need to read documents from one external account. Connect that account in the correct Workspace, then explicitly assign the supported integration to the Agent. Review which provider permissions and operations are involved before using it.

In the Agent's Composer, identify the desired collection or records and the result you want. You can [mention the Connector](/docs/composer/mentions) to make the reference explicit, but the mention does not replace assignment.

The Agent's membership in the Workspace or association with a Project is not a substitute for this setup. Likewise, a Project's development connection does not automatically authorize its production Site.

## Change or remove access

Removing a resource assignment and disconnecting the underlying account have different effects. The assignment concerns one consumer; the account may support several consumers. Review those dependencies before removing shared access.

Use the secure account-management flow to reconnect or update credentials. If you intend to change providers for a managed capability, use that capability's provider-selection workflow. Adding a new account alone does not switch an existing database, storage resource, or model provider.

For active work, changes to access remain subject to current authorization checks. Revocation can prevent further use, but it cannot retract a message already sent or reverse another completed provider action.

## Keep credentials out of content

Operator tools use authorized gateways and safe operation metadata rather than retrieving provider tokens. Keep secrets out of Instructions, Skills, Files, client code, logs, and published templates.

Application code can have separately configured server-side credentials when its architecture requires them. Those belong to the trusted development or production scope, not the operator's ordinary conversational context.

## Resolve access problems

| Problem | Check |
| --- | --- |
| Account is connected but unavailable | Assignment and eligibility for the receiving resource |
| Authentication expired | The supported reconnect or credential-update flow |
| Development works but production fails | Independent Site configuration and credentials |
| Operation is denied | Provider permissions, resource access, and current approval |

If a write times out, inspect the external destination before retrying. For example, check whether the intended record was created before submitting the same creation request again. A missing response is not proof that the service made no change.

A [remix](/docs/marketplace/remix) carries safe setup requirements, not the creator's account binding. Each recipient authorizes their own connection.