Settings Integrations
Open Settings → Integrations in the active Codity account. These connections supply review context and issue workflows. Repository onboarding uses the separate provider guides; a Slack connection, Jira token or model-provider key does not connect a GitLab repository.
Available Connections
Select an integration in the integration navigation. Controls depend on the account provider, plan features and your access. A hidden or locked card is not evidence that a credential is invalid.
| Connection | Configuration in Codity |
|---|---|
| Jira | Site URL, email and API token; Test Connection and Save Settings. |
| Linear | API key; Test Connection and Save Settings. |
| Confluence | Site URL, email, API token and optional MCP server configuration; Test Connection and Save Settings. |
| ClickUp | API Token, optional Workspace / Team ID and comma-separated List IDs. Test Connection, then Save Settings. List IDs support task lookup by PR title when no task is linked. |
| Notion | Internal integration token. Grant the integration access to the pages to be read; entering a token alone does not share those pages. Test Connection, then Save Settings. |
| Azure Boards | Available in the Azure account context. Organization and Personal Access Token; use the displayed access requirements and the Azure provider guide. Test Connection, then Save Settings. |
| GitHub Issues | Available in the GitHub account context; uses the connected GitHub App, without another credential form. |
| GitLab Issues | Available in the GitLab account context; uses the connected GitLab PAT, without another credential form. |
| Slack | Connect Slack through workspace consent; an account administrator manages the connection. |
Enable and Verify
Enable the relevant integration toggle where offered, enter credentials only into the dedicated form and check the saved state. Test Connection checks the current connection; it does not guarantee access to every private ticket/page or permission to create issues. Link a permitted item in an eligible PR/MR and inspect whether the review includes its context.
Review-context read access and issue creation are separate operations. See Create issues from review comments before enabling a write workflow. Prefer credentials limited to the work they need to perform, and replace/revoke them through their provider when required by your organization.
