Integrations

Integrations → Integrations (/admin/settings/integrations). What appears depends on plan and deployment

GitHub authentication health

On workspaces that sign in with the GitHub App, a read-only panel shows the provider, the connected organisation or account, admin and team sync status, last successful syncs and errors

GitHub and Linear credentials

On Team and Enterprise, Trackers holds a GitHub personal access token and a Linear API key; with them, linked work items carry issue and PR titles and status. On Free the section is GitHub integration only. Each has its own Save; kcap validates the credential with the provider before storing it encrypted. Clear confirms before removing. If work-item projection events have failed, a warning shows how many and Rebuild work items projection requests a rebuild at the next restart

Slack

One Slack app gives session and agent links a preview card and, where notifications are on, delivers direct messages. It has no slash commands

1. Set up (or Reconfigure). Create Slack app opens Slack with a manifest prepared for your server; or paste it into Create New App → From a manifest. Choose the workspace, create the app, and install it under OAuth & Permissions. For an existing app, replace its manifest and reinstall; Slack only grants new scopes on reinstall
2. Paste the Signing Secret (Basic Information) and Bot User OAuth Token (xoxb-…, OAuth & Permissions) and Save and validate. Both are stored encrypted
3. Optionally post a session link in a channel the app is in and Check that the signed event arrived

Organisation-visible and public sessions unfurl with their summary; private, project-only and scoped sessions unfurl as a lock placeholder, because Slack has no signed-in viewer. Direct-message notifications readiness shows whether the app’s scopes allow DMs; each person opts in from their own notification settings

Behind a reverse proxy that changes the host, set Slack:PublicOrigin so the manifest carries the public URL; the page warns when the saved manifest origin differs from the current one. To stop the integration, uninstall the app from Slack

Machines

Integrations → Machines lists machine credentials with name, client id, role, creation date and Active or Revoked. Revoke stops a machine’s access; the row stays for audit. Creation is in the CLI, so the secret never passes through the server: Store sessions where nobody can sign in