Skip to main content
You want to ask Ankra AI about a failing deploy from the chat tool your team already uses, and have its approvals and findings reach people there. Every chat app and code host Ankra AI talks through is connected on Ankra AI → Gateway connections (/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.
A new Slack or Teams connection starts in the mode set by How new chat connections start on Ankra AI → AI workspaces, which is Ask unless an admin changes it. Code host connections do not follow it: they start with every capability off, see AI code review. Your own Slack, Teams, GitHub and Bitbucket accounts, and the notifications you get there, are on Connected accounts under your account, not here. See User profile.

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.
1

An owner or admin installs the app

On Ankra AI → Gateway connections, in the Slack section, press Add to Slack (Add a workspace once one is connected). Slack asks you to approve the app for your workspace and sends you back to Ankra, which says The Slack workspace is connected. The workspace now shows as a row in the Slack section.If you see Slack was not connected: the installation was not finished. Try again., press Add to Slack again.From a terminal, the admin runs 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.
Check it with 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.
2

Each person links their own Ankra account

The first time someone mentions @Ankra, sends it a direct message, runs /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.
3

Set the AI mode

Pick Ask or Agent on the workspace’s row. In Ask mode, the buttons that change something - acknowledging an alert, approving a remediation, working a ticket - are refused.
4

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: It does not ask for email addresses, files, or anyone’s direct messages with other people.

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 status shows whether you are linked, /ankra logout disconnects you, and /ankra help shows what it can do. Anything else after /ankra shows 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.
Every button runs as your Ankra user through your own linked account, so your role decides what it may do and the audit log records your name.

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.
If your tenant restricts Teams Store apps and your Teams administrator is someone else, send them the ready-made message below. It covers everything they need to do.
1

Install Ankra AI from the Microsoft Teams Store

Ankra AI is published on the Microsoft Teams Store:
  1. In Teams, open Apps.
  2. Search for Ankra AI.
  3. Press Add.
On Ankra AI → Gateway connections, the Microsoft Teams section’s Connect a tenant card (Connect another tenant once one is connected) has Get it from the Teams Store and Or open it in Teams, which take you to the same app.
If Ankra AI does not appear in the search, or Teams says it needs approval, your tenant restricts Store apps. A Teams administrator allows it once in the Teams admin center under Teams apps → Manage apps: search for Ankra AI and press Allow. Under Teams apps → Permission policies, they also check that the people who should use it are allowed to. The ready-made message covers both steps.
2

An Ankra owner or admin connects the tenant

  1. In Teams, add Ankra AI to a team, group chat, or personal chat.
  2. The bot sends you a welcome card with a claim code. Press Connect to Ankra.
  3. Gateway connections opens with Claim code received from Microsoft Teams and the code already in the Claim code field. Press Connect.
The card now says the tenant is connected, and the tenant shows as a row in the Microsoft Teams section. This tells Ankra which organisation’s clusters this Teams tenant may see.Good to know:
  • 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.
3

Each person links their own Ankra account

Message the bot, or mention @Ankra AI in a channel, then press Connect Ankra account and sign in with your normal Ankra login. You only do this once.This is per person on purpose: the bot answers with your Ankra permissions, and your name, never the bot’s, is what appears in the audit log.
4

Optionally, set the AI mode

Pick Ask or Agent on the tenant’s row. Ask is read-only, and Agent lets Ankra AI act.
5

Optionally, send alerts and pipeline notifications to a Teams channel

Once the bot is in a team, a Microsoft Teams notification destination (Integrations & alerts → Notification destinations) can post to that team’s channels. The bot posts the card itself, so you don’t need a Power Automate URL. Add the bot to every team whose channels should receive notifications. If a team the bot is already in lists no channels, mention @Ankra AI once in that team and reload.Apart from alerts that list it as their own destination, a destination only receives what a notification route sends it, so add a route for each kind of notification the channel should hear. For pipeline runs, route the pipeline notification kinds. From the CLI:
The first route sends pipeline failures, approval requests, blocked images and failed previews; the second adds every critical notification, except opt-in kinds such as 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:
The app package is only for tenants that block Store apps. It installs the same Ankra AI bot as the Store listing. The Connect a tenant card on Gateway connections links to it as upload the app package, under Store apps blocked in your tenant?

What your Teams administrator will want to know

Only in teams it was added to, and only to answer. With version 1.1.0, Teams delivers that team’s channel messages to the bot, which:
  • Answers only messages that @mention it. 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.
With earlier versions, it only receives @mentions and direct messages.
The messages people send to the bot, the thread a mention was made in (version 1.1.0), and replies in threads that mirror an Ankra board ticket, plus the IDs needed to reply (tenant, conversation and user). These reach the Ankra platform so the assistant can answer, and the conversation is stored against your Ankra organisation. Unmentioned channel messages outside those threads are not stored or exported.
No. The bot runs in Ankra’s platform and talks outbound to Microsoft’s Bot Framework, which relays to Teams. Nothing connects inbound to your network, and there is no IP range to allow-list.
The person using it. Every answer and button runs with that person’s own Ankra permissions and is recorded under their name in your organisation’s audit log. Someone who has not linked an account gets a connect prompt instead of an answer. An Ankra owner or admin can also limit what the integration may do with the AI mode on the tenant’s row (Ask for read-only, Agent to let it act).
In the Teams admin center: Manage apps → Ankra AI → Block. If you uploaded the app package instead of using the Store, delete it from your org’s catalog. In Ankra: Ankra AI → Gateway connections, press Disconnect on the tenant’s row and confirm Disconnect tenant. Ankra AI stops answering there, and the people linked there stop getting notifications.

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.
Every button runs as your own linked Ankra user. Instead of /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

To post alert cards to Teams without the bot, use a webhook destination with the Adaptive Card template instead. See Microsoft Teams webhooks.

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 with ankra 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 with ankra 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 projects core and tools and channels #ankra-core and #ankra-tools:
  1. Create one catch-all route in each project, This project, sending to that project’s channel.
  2. 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.
The organisation’s own routes and channels stay the fallback in three cases:
  • 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.
The walkthrough is one channel per project.
The bot’s answers in a project channel still come from your default project, and remediation approval cards still go to the organisation’s Slack remediation destination.

Permissions

Connecting and disconnecting Slack and Teams, changing an AI mode, and changing ticket sync connections need an owner or admin. Destinations and routes need alerts.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.