/next/ai/settings/gateway). The page has one section each for Slack, Microsoft Teams, GitHub, GitLab and Bitbucket, then Review instructions and Tools, tickets and notifications.
Ankra AI → Gateway (/next/ai/gateway) is the overview: which surfaces are connected, and Set up the gateway to connect them in order. See Set up the AI Gateway. How a message travels from Slack or a pull request to Ankra AI and back is explained in AI Gateway. To put it all to work during an incident, follow Ankra AI on call in Slack or Microsoft Teams.
Before you start
- An owner or admin role to connect or disconnect a chat app and change its AI mode. Everyone else sees the connections, and each section says Only organisation owners and admins can connect or disconnect chat apps and change their AI mode.
- A Slack workspace or a Microsoft 365 tenant where you may add apps. For Teams, you may need your Teams administrator; see Connecting Microsoft Teams.
Slack and Microsoft Teams
Each connected Slack workspace or Teams tenant is one row, with Connected and the date, the number of linked people, and its own AI mode - what Ankra AI may do when talked to from there:- Ask reads, and makes only low-risk new things. Buttons that change something are refused.
- Agent can make changes, with the permissions of the person asking. The row is marked Can act.
Connecting Slack
Slack takes one Ankra owner or admin to install the app, then each person links their own Ankra account the first time they use it.An owner or admin installs the app
ankra slack connect instead. It prints the install address and waits until the install finishes; open the address in any browser and approve it there. It needs a person’s token, not a service account’s.ankra slack status, which lists the connected workspaces.The install link lasts 10 minutes from the moment you press Add to Slack. Start the install from Ankra, not from Slack: that is what tells Ankra which organisation’s clusters the workspace may see. An install started from Slack ends on a One more step page instead, and Continue in Ankra there starts it from Ankra. One Slack workspace links to one Ankra organisation, and installing it from a different organisation revokes every account link in it.Each person links their own Ankra account
/ankra, or presses one of its buttons, Ankra replies to them alone with Connect Ankra account. They sign in with their normal Ankra login and confirm the Slack user and workspace shown, and Ankra then answers the question they asked. The row’s count of linked people goes up by one.This is per person on purpose: the bot answers with that person’s Ankra permissions, and their name - never the bot’s - is what lands in the audit log.Set the AI mode
Optionally, choose a home channel
What the Slack app can see
The app receives messages that mention it, direct messages sent to it, and messages in channels it has been added to. It uses a channel message only when it is a reply in a thread that already holds an Ankra conversation or an Ankra ticket, so you can follow up without mentioning it again. Every other channel message is dropped as it arrives and is never stored. The first time it is mentioned inside an existing thread, it reads up to 50 of that thread’s replies once, so it can see the alert or error you were already discussing. Those replies are kept with the conversation in your Ankra organisation, like the question itself. It asks Slack for these permissions and no others:What the bot can do in Slack
- Ask it anything - mention @Ankra in a channel, message it directly, or open it in Slack’s assistant pane. Say
use cluster <name>to scope the thread to one cluster. An answer in a channel is visible to that channel. /ankra- on its own it links your account./ankra statusshows whether you are linked,/ankra logoutdisconnects you, and/ankra helpshows what it can do. Anything else after/ankrashows the same help, because a question typed there does not reach Ankra AI: mention the bot or message it instead. Sending it help as a message shows the help too.- Act on alerts - alert cards carry Acknowledge and Snooze 1h buttons, and AI remediation approvals carry Approve and Deny (Approve all and Deny all for a batch). A decided card is replaced by its outcome.
- Approve Ankra AI’s writes - when a turn proposes a change that needs confirmation, the bot posts a Confirmation needed card with Confirm and Deny. Only the person who asked can decide it, and if the cluster changed in the meantime the card shows what moved and offers Confirm anyway.
- Work tickets from the thread - an escalated ticket’s thread carries Assign to me and, while a plan is awaiting a verdict, Approve plan and Request changes. A reply in a ticket’s thread is added to the ticket as a comment.
Ankra’s home channel
The home channel is the Slack channel Ankra posts in when something important happens and no notification route matches it: failures, agents going offline, security findings. Only critical and warning notifications fall back to it. Set it on Ankra AI → AI workspaces, on the Ankra’s home channel in Slack card: pick a channel and press Save home channel. The card now reads The home channel is followed by the channel. Clear the home channel removes it. The card needs a connected Slack workspace, and changing it needs an owner or admin; everyone else sees the current channel.Disconnecting Slack
- For the whole workspace - an owner or admin presses Disconnect on the workspace’s row on Gateway connections and confirms Disconnect workspace. Ankra AI stops answering there, and the people linked there stop getting notifications. Uninstalling the app from Slack has the same effect.
- For yourself - run
/ankra logout, or press Disconnect in the app’s Home tab in Slack.
If Slack does not work
Connecting Microsoft Teams
Teams setup involves up to three people. Agree who is who before you start: most delays come from one person waiting on another without knowing it.Install Ankra AI from the Microsoft Teams Store
- In Teams, open Apps.
- Search for Ankra AI.
- Press Add.
An Ankra owner or admin connects the tenant
- In Teams, add Ankra AI to a team, group chat, or personal chat.
- The bot sends you a welcome card with a claim code. Press Connect to Ankra.
- Gateway connections opens with Claim code received from Microsoft Teams and the code already in the Claim code field. Press Connect.
- The card arrives in a personal chat. Whoever redeems the claim code connects the whole tenant, so the code is never posted in a channel. If you add the bot to a team or group chat, it messages you privately and tells the channel who got the code. Anyone else can get it by opening a personal chat with Ankra AI and saying hi.
- Typing the code by hand also works. The welcome card shows the code. On Gateway connections, type it into Claim code on the Connect a tenant card and press Connect.
- The code lasts up to 24 hours. Asking the bot again returns the same code until it is close to expiring, so a colleague talking to the bot won’t invalidate yours.
- One tenant, one organisation. A Microsoft tenant connects to exactly one Ankra organisation, while one organisation can connect several tenants. If a tenant was connected to the wrong organisation, disconnect it there and message the bot for a new code.
Each person links their own Ankra account
Optionally, set the AI mode
Optionally, send alerts and pipeline notifications to a Teams channel
application_down, which a route must name. Add pipeline_run_succeeded or preview_ready only if the channel wants every green run and every pull request preview that comes up: the first fires once per green run, the second when a preview becomes reachable. Without --organisation-wide, a route delivers only your current project’s notifications. Check where a notification would go with ankra alerts routes preview --kind pipeline_run_failed.What to send your Teams administrator
Copy this as is:What your Teams administrator will want to know
Does it need admin consent or Graph permissions?
Does it need admin consent or Graph permissions?
ChannelMessage.Read.Group. A team owner grants it for their own team when they add the app; it never covers other teams. Whether team owners may grant RSC is a tenant setting; see Microsoft’s resource-specific consent guide. Adding version 1.1.0 to a team means granting it: Teams does not let a team owner decline one permission and keep the app. If your tenant blocks team owners from granting RSC, they cannot add this version until an administrator allows it. Versions before 1.1.0 declare no RSC permission. Manage apps shows which version your tenant has.Can it read our channel history?
Can it read our channel history?
- Answers only messages that
@mentionit. Everything else in a channel goes unanswered. - When mentioned inside a thread, reads that thread so it knows what “this” refers to, for example the alert card the thread started from.
- Copies a plain reply onto an Ankra board ticket’s timeline only when the thread mirrors that ticket, and ignores every other unmentioned message.
@mentions and direct messages.What data leaves Microsoft Teams?
What data leaves Microsoft Teams?
Does it need a firewall or network change?
Does it need a firewall or network change?
Who does it act as?
Who does it act as?
How do we remove it?
How do we remove it?
What the bot can do in Teams
The same as in Slack:- Answer questions. Say
use cluster <name>to scope a conversation to one cluster. - Act on alert cards.
- Confirm or deny Ankra AI’s proposed changes.
- Work tickets from their thread.
/ankra, type help, status, connect or logout to the bot. status (or whoami) shows a card with your connection and a Connect or Disconnect button. login works for connect, and signout or disconnect for logout. Slack accepts the same words.
If something does not work
GitHub, GitLab and Bitbucket
Connect GitHub (through the Ankra GitHub App), GitLab, or Bitbucket Cloud in their sections on Gateway connections so Ankra AI can read repositories, review pull requests, answer@ankraai mentions, and power PR preview environments.
Every capability is off on a new connection: connecting a provider grants access and nothing else. How to connect each one, what each switch does, how per-repository rules override the connection-wide defaults, what a review posts, and when one is skipped are all covered in AI code review.
MCP Tool Servers
Register your own MCP servers to give Ankra’s agent runs extra tools. Each server exposes its tools after a health probe, and every tool needs an explicit role grant before runs can call it - registering a server grants nothing by itself. The portal has no page for MCP tool servers. Register and grant them withankra org mcp-servers, or with the tools in the Agent MCP Tool Servers reference. Managing them needs an organisation admin.
--secret-header stores the header’s value in an organisation secret and registers the server with a reference to it, so the value never lands in the server record. See ankra org mcp-servers for every flag.
This is the opposite direction from Ankra’s own MCP Server, which lets your MCP client - Claude, Cursor, or your own agent - call Ankra. To have your own agent pick up and work board tickets, see Work the AI board with your own agent.
Ticket Sync
Mirror AI board tickets into a Jira project, a Linear team, or your own webhook endpoint. The external issue is created once per ticket and timeline events follow as comments. Each connection carries its own filters for ticket kind, minimum priority, and whether timeline events are relayed at all. Sync is one-way: edits and comments made in the tracker do not come back to the board. The portal has no page for ticket sync. Set it up withankra tickets sync connections create; Sync board tickets to Jira, Linear, or a webhook shows where each provider value comes from, the webhook payload contract, and troubleshooting.
Outbound Delivery
Where Ankra’s notifications go is set outside the Ankra AI menu, under Integrations & alerts:- Integrations & alerts → Notification destinations (
/next/organisation/notification-destinations) - the Slack channels, Teams channels and webhook endpoints that receive platform events, with ready-made templates for Slack, Teams, Discord, and PagerDuty, or a custom JSON payload template. Send a test in a destination’s menu checks the wiring. See the webhook guide for payloads and templates. - Integrations & alerts → Notification routes (
/next/organisation/notification-routes) - rules that decide which events (alerts, security findings, agent status, GitOps) go to which destination. Critical and warning events with no matching route fall back to the home channel, except the opt-in kinds, which only a route naming them delivers. See Notification routing for matching, ordering, and the one-delivery-per-destination guarantee.
A Slack or Teams channel per project
A route in a project delivers only that project’s notifications; an organisation-wide route delivers every project’s and the organisation’s own. With projectscore and tools and channels #ankra-core and #ankra-tools:
- Create one catch-all route in each project, This project, sending to that project’s channel.
- Bind the same channels under Project channels on the ticket desk’s Communication tab, so ticket threads with their approval, plan sign-off and decision buttons land there too.
- A notification not tied to a project, such as billing, reaches only organisation-wide routes.
- A notification that matches no rule at all goes to the home channel, and only when it is critical or warning and not an opt-in kind.
- A ticket whose project binds no channel for Slack or Teams opens its thread in the organisation’s tickets channel for that provider.
Permissions
Connecting and disconnecting Slack and Teams, changing an AI mode, and changing ticket sync connections need an owner or admin. Destinations and routes needalerts.manage, MCP tool servers ai.manage; owners and admins hold both, and custom roles can grant them. Members see the connections and their settings. Ticket sync credentials are write-only: they are kept in Ankra’s secret store, never in the database, and are never returned to anyone.