Connections

Connections let CORA use context from the tools your team already works in, and take approved actions there.

Where to find them

Open Settings from the account menu in the lower left, then choose Connections. The library lists every connector as a card. Use the search field, or the filters All connections, Your connections, and the categories, to narrow the list. Select a card to open the connector's own page, with its capabilities, setup, and a Connect to CORA button when it is ready to connect.

Personal and workspace connections

Each connector shows who owns it:

• Personal connections, such as Microsoft 365 and Google Workspace, are your own account. Each member connects and manages their own. Other members cannot see or use your account unless you grant a specific resource to a process.
• Workspace connections, such as Slack, Discord, HubSpot, and Pipedrive, are company-level. Workspace owners and admins connect and manage them for everyone. Other members see Admin connects this.

Card states

• Connected means the connection is in place.
• Ready to connect means you can start setup now.
• Setup needed means the connector is not configured yet.
• Request access means the connector exists but must be enabled for your workspace first. Open it, write what you need under Request this connection, and choose Send request. The CORA team reviews it and replies on the same page. Approval enables setup; it does not connect an account for you.
• Planned means the connector is not available yet. You cannot connect it or use its functions.

Actions need approval

CORA uses a connection through named actions, such as Send Outlook mail or Post to Slack. Each action has its own approval rule in Settings -> Agent permissions. External actions wait for a person's approval: you see the proposed action before it runs, and a workspace can make an action stricter but never looser than its default.

CORA never shows stored credentials, and disconnecting a connection stops CORA from using it.