Integrations

Integrations is where a workspace connects to everything outside ACE: cloud accounts, Git providers, and the chat and issue tools your team already uses. Think of it as the platform's plug panel. Almost nothing that reads an external system or posts into one works until the connection exists here first. Knowledge's Discovery step needs a repository, infrastructure discovery needs a cloud account, and agent updates in Slack or Microsoft Teams need a connected app.

What are the three surfaces?

The section splits into three surfaces, one per kind of provider. They all share the same connect, reconnect, and disconnect machinery underneath.

1. Clouds: AWS, GCP, and Azure, connected with pasted read-only credentials. Powers infrastructure discovery.
2. Repositories: GitHub and GitLab. Connect a provider account, then import specific repositories into a project. Powers Knowledge's code mapping, Pull Requests, and Deployments.
3. Communication: Slack, Microsoft Teams, Linear, and Jira. Lets agents post updates, read issues, and notify the right channel.

What's shared across all three

• Workspace scope. Every connection belongs to exactly one workspace, never to your personal account. Each page is blocked behind a "select a workspace" prompt until one is active.
• Multiple accounts per provider. You can connect more than one account of the same provider (two AWS accounts, two GitHub orgs, two Slack workspaces) and pick which one serves which project.
• One account per provider per project. Repositories and Communication both enforce that a given project uses at most one account of a given provider at a time; assigning a different one replaces the old assignment rather than stacking it.
• The same connect mechanics. Most providers connect through an OAuth popup (opened via Nango, the credential vault behind every connection); GitHub and GitLab additionally accept a pasted personal access token. Cloud providers are the one exception: they never use OAuth, only pasted credentials (see Clouds).
• The same failure surface. A broken credential (expired token, revoked key, changed scopes) shows as a red error strip directly on the affected account, with a reconnect action next to it, on whichever of the three pages that account lives.
• The same permission split. Seeing a page's connections needs org:integrations:read; changing anything (connect, reconnect, disconnect, reassign) needs org:integrations:manage, which requires org:integrations:read as a dependency. Repositories layers a second, project-scoped permission (repo:read / repo:manage) on top for the repository list itself.

Where to find it

Left sidebar → Integrations, containing Clouds, Repositories, and Communication. Clouds and Communication are workspace-scoped pages; Repositories additionally scopes its repository list to whichever project you have selected. All three are also reachable as link-out cards from Settings → Workspace → Connections (see Connections).

How this connects to the rest of the platform

• Knowledge: Discovery's "Map code" step requires a connected repository (Repositories); its infrastructure census and Investigate step require a connected cloud account (Clouds).
• Pull Requests and Deployments: both are populated live from repositories connected on Repositories.
• Inbox → Notification delivery: a project's linked Slack channel (set up on Communication) is one of the delivery rows there.
• Workspaces: connections are managed per workspace, and the Owner and Admin roles described there are what grant org:integrations:manage in the first place.