Connect workplace apps to Cortex
Connect workplace apps to Cortex and manage their access, credentials, connection health, and shared business context.
Connect each workplace app once for the organization. Connections add company context to AI activity; capture works without them. For AI tools captured by Cortex Defender, use the supported AI tools catalog.
Before you begin
Required
- Organization admin access
Use an admin account for the intended Cortex organization.
- Source app permissions
Have permission to authorize the source app. Grant Cortex access only to content everyone in the organization is allowed to use. The app setup guides list each app's authorization requirements.
Connection scope and visibility
These are organization-wide connections. Source permissions determine what a connector can read; Cortex roles and visibility are separate settings. Connecting an app does not replace them. Select content appropriate for everyone in your Cortex organization.
Where to connect apps
Open Organization → Apps. If you manage multiple organizations, open the organization under Admin → Organizations, then select Apps.
| Field | Meaning |
|---|---|
| Scope | Whole org for self-service connections |
| Credential | Set when Cortex holds the credential |
| Status, connection state | Connection state: active or revoked |
| Status, authorization state | Read the authorization result and follow any verification or reauthorization instruction. |
You can also connect apps during organization setup.
App setup guides
| App | Content available to the connection | Authorization |
|---|---|---|
| GitHub | Pull requests, issues, and commit metadata from selected organization repositories. | GitHub App installation |
| Jira | Projects and issues from one Jira site, within the account's access. | Atlassian OAuth |
| Linear | Teams, projects, and issues from one authorized workspace. | Linear OAuth |
| Asana | Tasks, subtasks, and comments from projects the token can see, with each task's Asana access. | Service Account or personal access token |
| Fibery | Entities and comments from account-visible, non-system databases. | Workspace API key |
| Granola | Meetings in shared spaces, with their AI summaries, transcripts, attendees, and folders. | Workspace API key |
| Notion | Pages shared with the integration, narrowed by Configure pages. | Internal integration token |
| Slack | Channel messages. Organization-wide Search includes captured public-channel content. | Bot and app-level tokens |
Connect Jira or Linear
Use an account that can access the intended Jira site or Linear workspace. Both connections are read-only and limited to the authorizing account's access.
Jira
- In Organization → Apps, add Jira.
- Sign in to Atlassian and approve read access to Jira work and users, plus offline access so the connection can stay active.
- Choose the Jira site if your account can access more than one.
- Return to Cortex and select Test & preview. It lists non-archived projects from that site.
Each connection covers one Jira site.
Linear
- In Organization → Apps, add Linear.
- Sign in to Linear, approve read access, then return to Cortex. Authorization lets the connection stay active.
- Select Test & preview to inspect teams and projects from that workspace.
Each connection covers one Linear workspace and its teams; Cortex sees only issues available to the authorizing account.
Manage an existing connection
In Organization → Apps, open the connection's Manage menu:
- Run Test & preview after any change made in the source app. It reports connection health and a limited sample of accessible content.
- Update app-specific settings, such as Configure pages or Configure channels.
- A connection needing reauthorization offers Reauthorize instead of Test & preview. Select Reauthorize when Jira or Linear invalidates its authorization, then run Test & preview again.
- Select Revoke to stop future use of a connection.
- Select Delete to remove a connection.
Select Edit connection on Notion, Slack, Fibery, Granola, or Asana to update tokens. Existing tokens show Stored. Optional Slack tokens also have a Remove action. Paste only the tokens you are replacing.
Cortex never displays saved token values. Keep each token in your approved secret manager.
GitHub: See GitHub connection management for repository selection, token storage, app removal, and retained metadata.
Slack: See Slack connection management for app removal and retained messages.
Get help
Contact the Chaos Labs team when a connection cannot be authorized, or when Test & preview does not list what you expect. Include the app, the Cortex organization and the approximate attempt time. Never include a token value.