Skip to documentation
Documentation
Documentation
OverviewInstallationQuickstartYour first dayYou were sent a linkWorking with a customerConfigurationTroubleshootingFAQGlossary

Usage

Terminal interfaceCLIStatuslineDashboardAnalytics

Collaborate

DocumentsLessonsSession sharingPicking up tomorrow and handing work overFrom your phoneSession linksSession messagingAsksAsks privacy fact sheetFeedbackEmail from crewkitBlueprintsAgent identitiesMCP server

Configure

AgentsSkillsSkill and agent security scanningRulesCommandsInheritancePlaybooksExperimentsHooksCapture modesSensitive sessionsData residencyTeamSettings mapIntegrations

Workspaces

WorkspacesSet up a workspaceFix a ticket end to endShip a feature with approvalHand off work and set agent settings

API Reference

API OverviewAuthenticationSessions APIResources APIOrganizations APIProjects APIPlaybooks APIExperiments API
Need a hand?Find an answer in troubleshooting.
Loading docs…
CREWKIT / DOCUMENTATION

Integrations

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.


Organization

IntegrationWho connects itWhat it reads and writesSteps
GitHub (the crewkit GitHub App)Admin and up installs and disconnects it; Manager and up picks its repositoriesReceives 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 projectsThe 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 itSearches 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 itLets 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 configurationSigns 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.

Settings map

The settings listed here, the level it applies at, who may change it, its default and what changing it stops.

Workspaces

Plan and ship work across several repositories, keyed to Jira cards.

On this page

OrganizationPersonProject
IntegrationWho connects itWhat it reads and writesWhere
Google DriveAny memberRead-only access to Drive. Imports the files the person picks as documents of a project. Never writes to Drive.A project's Documents
Slack accountAny member, once the organization has installed SlackRecords which Slack user the person is in the organization's Slack workspace. Keeps no Slack token.Their profile
GitLab accountAny memberRecords 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.
  • Feedback keys: let an app you test send reports to the project. See Feedback keys.

Who may change each one is on the settings map.