An integration connects crewkit to a tool your team already uses. It connects at one level: the organization, a person or a project. An organization integration holds the credential; a project only says which of the organization's repositories, channels or keys it uses.
Organization integrations are in Integrations in the sidebar unless the row says otherwise. For every other setting, see the settings map.
Organization
| Integration | Who connects it | What it reads and writes | Steps |
|---|---|---|---|
| GitHub (the crewkit GitHub App) | Admin and up installs and disconnects it; Manager and up picks its repositories | Receives the events of the repositories the App is installed on, such as a pull request opening, merging or closing. Under the minimal capture mode, or in a resident organization, crewkit keeps no text of those pull requests and issues. | Connect your code host |
| GitLab (a top-level group) | Admin and up connects it and links its projects | The same events as GitHub, for each linked GitLab project. Linking a project registers its webhook. | Connect your code host |
| Jira (a service account) | Admin and up connects and disconnects it; Developer and up searches and creates issues through it | Searches Jira and creates issues; reads the status of linked cards every 15 minutes. The API token is stored encrypted. | Connect Jira |
| Slack (a workspace) | Admin and up installs, changes and removes it | Lets a project's team agent read and reply in its channels, and lets work items post to a channel. | Give the workspace a Slack agent |
| Single sign-on and SCIM (in Settings → Single sign-on) | Owner only adds, changes or removes an identity provider or a SCIM token, and verifies a domain; Admin and up can view the configuration | Signs members in through your identity provider, and creates and removes members from it. | Single sign-on and SCIM |
Person
Each person connects these for themselves, and only that person can use or remove the connection.