Skip to main content
You want to ask Ankra’s AI about a failing deploy from the chat tool your team already uses, and have its approvals and findings reach people there. The Connections section under AI → Settings → Connections gathers every integration the AI communicates through, in five groups.

​
Chat & Notifications

  • Slack - install the Ankra app into your workspace. See Connecting Slack below.
  • Microsoft Teams - connect your tenant and add the Ankra bot to the teams that should reach the AI. See Connecting Microsoft Teams below.
Each connection carries its own AI mode - what the AI may do when talked to from that surface. A Slack or Teams connection with no mode of its own follows the organisation-wide Default AI mode on the Workspaces settings page, which is Ask unless an admin changes it. Source-control connections do not follow it: they start with every capability off, see AI code review.

​
Connecting Slack

Slack takes one Ankra organisation admin to install the app, then each person links their own Ankra account the first time they use it.
1

An Ankra organisation admin installs the app

Under AI → Settings → Connections → Chat & notifications, press Add to Slack on the Slack card (Add workspace once one is connected). Slack asks you to authorise the app for your workspace and sends you back to Ankra, which confirms Slack workspace connected.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. 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.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

Each workspace row carries an AI mode control. Ask is read-only, plus low-risk creations. Agent lets the AI act, and marks the row Can act. A workspace with no mode of its own follows the organisation’s Default AI mode on the Workspaces settings page, which is Ask unless an admin changes it. 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

See Ankra’s home channel below.
The app requests the Slack permissions it needs to answer mentions and direct messages, post replies and cards, run /ankra, look up the Slack user who asks, and list channels for the home channel picker. It receives messages that mention it, direct messages, and its App Home - it does not receive the rest of a channel. When it is mentioned inside an existing thread, it reads that thread’s replies as context.

​
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.
  • 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 the 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 to when something important happens and no notification route matches: failures, agents going offline, security findings. Only critical and warning notifications fall back to it. Set it under AI → Settings → Workspaces, on the Ankra’s home card: pick a channel and press Save home channel, or Clear to remove it. The card needs a connected Slack workspace, and changing it needs organisation admin; everyone else sees the current channel.

​
Disconnecting Slack

  • For the whole workspace - an Ankra organisation admin presses Disconnect on the workspace row. Every linked user in that workspace loses their connection and stops receiving 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 Teams administrator is someone else, send them the ready-made message below. It covers everything they need to do.
1

The Teams administrator makes the app available

Ankra AI is not in the Microsoft Teams store, so it is uploaded as an app package:
  1. Download the package from https://ankra-gateway.ankra.app/teams/app-package. It is a small .zip with the app manifest and icons, and the link needs no Ankra login.
  2. In the Teams admin center, go to Teams apps → Manage apps → Upload new app and select the .zip.
  3. Under Teams apps → Permission policies, check that the people who should use it are allowed to.
In the Ankra portal, the same package is under AI → Settings → Connections → Microsoft Teams as Download package, with Copy link for a Teams admin beside it.
People can also upload the app for themselves (Apps → Manage your apps → Upload an app), but only if your tenant allows custom app uploads. Most enterprises turn that off, so the admin route is the reliable one.
2

An Ankra organisation 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. Press Connect to Ankra.
  3. The Ankra portal opens with the claim code already filled in. Press Connect.
That’s it. 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.
  • Pasting the code by hand also works. The card shows the code. In the portal, open AI → Settings → Connections → Microsoft Teams, press I already have a claim code, and paste it.
  • 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

The Teams card carries an AI mode control. Ask is read-only, and Agent lets the AI act. With no mode of its own, the tenant follows the organisation’s Default AI mode, which is Ask unless an admin changes it.
5

Optionally, send alerts to a Teams channel

Once the bot is in a team, alert Destinations let you pick a Team / Channel, the same way as for Slack. The bot posts the alert card itself, so you don’t need a Power Automate URL. Add the bot to every team whose channels should receive alerts.

​
What to send your Teams administrator

Copy this as is:

​
What your Teams administrator will want to know

No. The bot only receives messages addressed to it: an @Ankra AI mention, a reply in a thread it is already part of, or a direct message. It does not request the resource-specific consent that would grant access to channel messages.
Only the messages people send to the bot, 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. Nothing else is read 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 organisation admin can also limit what the integration may do with the AI mode control on the Teams card (Ask for read-only, Agent to let it act).
In the Teams admin center: Manage apps → Ankra AI → Block, or delete it from the catalog. In Ankra: AI → Settings → Connections → Microsoft Teams → Disconnect, which revokes every linked user’s access for that tenant.

​
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 the AI’s proposed changes.
  • Work tickets from their thread.
Every button runs as your own linked Ankra user. Instead of /ankra, type help, status or logout to the bot.

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

​
Source Control & AI Review

Connect GitHub (via the Ankra GitHub App), GitLab, or Bitbucket Cloud so the 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. 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 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.

​
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. See Sync board tickets to Jira, Linear, or a webhook for where each provider value comes from, the webhook payload contract, and troubleshooting.

​
Outbound Delivery

  • Destinations - 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 delivery from the destination’s menu to verify the wiring. See the webhook guide for payloads and templates.
  • Notification routes - rules that decide which events (alerts, security findings, agent status, GitOps) go to which destination. Events with no matching route fall back to the home channel. See Notification routing for matching, ordering, and the one-delivery-per-destination guarantee.

​
Permissions

Connecting, disconnecting, and changing destinations, routes, or ticket sync connections requires organisation admin. Members can see the ticket sync connection list, but never the credentials, which are write-only and stored in Vault.