---
source: crewkit documentation
url: https://crewkit.io/docs/integrations-setup.md
title: "Integrations"
description: "The tools crewkit connects to, grouped by the level they connect at, with who may connect each one, what it reads and writes, and where its steps are."
---


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](/docs/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](/docs/workspace-setup#7-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](/docs/workspace-setup#7-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](/docs/workspace-setup#6-connect-jira) |
| **Slack** (a workspace) | Admin and up installs, changes and removes it | Lets a project's [team agent](/docs/agent-identities) read and reply in its channels, and lets work items post to a channel. | [Give the workspace a Slack agent](/docs/workspace-setup#8-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](/docs/team#single-sign-on-and-scim) |

## Person

Each person connects these for themselves, and only that person can use or remove the connection.

| Integration | Who connects it | What it reads and writes | Where |
|---|---|---|---|
| **Google Drive** | Any member | Read-only access to Drive. Imports the files the person picks as documents of a project. Never writes to Drive. | A project's **Documents** |
| **Slack account** | Any member, once the organization has installed Slack | Records which Slack user the person is in the organization's Slack workspace. Keeps no Slack token. | Their profile |
| **GitLab account** | Any member | Records the person's GitLab user id, so their pushes are attributed to them. Keeps no email, login or token. | Their profile |

## Project

A project holds no credential. It names what it uses from the organization's integrations:

- **Repositories**: which of the organization's GitHub or GitLab repositories belong to the project, in the project's **Settings**.
- **Jira key** and **Slack channel**: where work items find cards and post. See [Set the Jira key and the Slack channel](/docs/workspace-setup#5-set-the-jira-key-and-the-slack-channel).
- **Feedback keys**: let an app you test send reports to the project. See [Feedback keys](/docs/feedback#feedback-keys).

Who may change each one is on the [settings map](/docs/settings-map#project).
