Skip to main content
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 with Add to Slack. Once connected, the AI can hold conversations in channels, send approval requests, and post to the home channel chosen under Workspaces.
  • 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), defaulting to the organisation-wide mode set under Workspaces.

​
Connecting Microsoft Teams

Rolling Ankra AI out in Teams usually involves three people. Work out who is who before you start - most of the friction in a Teams rollout is one person waiting on another without knowing it.
1

Your Teams administrator makes the app available

Ankra AI is not in the Microsoft Teams store, so it is installed from an app package. Your Teams administrator publishes it once for the whole organisation:
  1. Download the package from https://ankra-gateway.ankra.app/teams/app-package - a small .zip containing the app manifest and icons. This link needs no Ankra login, so you can send it straight to an administrator who has no Ankra account. An Ankra admin finds the same package as Download package in the portal’s guided setup, with Copy link for a Teams admin beside it.
  2. In the Teams admin center, open Teams apps → Manage apps → Upload new app and select the .zip.
  3. Check your app permission policies allow it for the people who should use it (Teams apps → Permission policies).
Individuals can install it themselves instead, under Apps → Manage your apps → Upload an app, but only if your tenant permits custom app uploads. Most enterprises disable that, which is why the admin route above is the reliable one.See what your Teams administrator will want to know for the security questions they are likely to ask.
2

An Ankra organisation admin connects the tenant

Add Ankra AI to a team, group chat, or personal chat. It greets you with a welcome card carrying a Connect to Ankra button - press it and the Ankra portal opens with the claim code already filled in, so you only need to press Connect.The card also prints the claim code, so you can paste it by hand instead. AI → Settings → Connections → Microsoft Teams opens a three-step guided setup - download the package, upload it into Teams, add the bot and connect - and the claim code field is the last step. Press I already have a claim code to jump straight to it.This step needs Ankra organisation admin, and it happens once per Microsoft tenant. It is what tells Ankra which organisation’s clusters this Teams workspace may see.
3

Each person links their own Ankra account

Anyone who wants to use the bot messages it, or mentions @Ankra AI in a channel, and presses Connect Ankra account once. They sign in with their normal Ankra login.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.
4

Optionally, route alerts to a channel

Once the bot is in a team, alert Destinations offer a channel picker for Teams the same way they do for Slack: pick Team / Channel instead of pasting a Power Automate URL, and the bot posts the Adaptive Card itself. Add the bot to every team whose channels you want to route to.

​
What to send your Teams administrator

If your Teams administrator is a different person, this is the whole ask - copy it as is:

​
What your Teams administrator will want to know

No. A Teams bot only receives messages addressed to it: an @Ankra AI mention, a reply inside a thread it is already part of, and direct messages. It cannot read the rest of a channel, and it has no permission that would let it - the resource-specific consent that grants channel-message access is deliberately not requested.
The text of the messages people send to the bot, and the identifiers needed to reply (tenant, conversation and user ids). 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 on your side.
Only the person clicking. Every answer and every button runs with the linked user’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 rather than a bot-powered answer, and an Ankra organisation admin can cap what the integration may do at all 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. On the Ankra side, AI → Settings → Connections → Microsoft Teams → Disconnect revokes every linked user’s token for that tenant.

​
What the bot can do in Teams

Everything the Slack app does:
  • Ask it anything - mention @Ankra AI in a channel or message it directly. Say use cluster <name> to scope a conversation to one cluster.
  • help, status, logout - show what the bot can do, check whether your Ankra account is linked, and disconnect it.
  • Act on alerts - alert cards carry Acknowledge and Snooze 1h buttons, and AI remediation approvals carry Approve and Deny. A decided card is replaced by its outcome, so nobody can act on it twice.
  • Approve the AI’s writes - when a turn proposes a change that needs confirmation, the bot posts a card with Confirm and Deny. Only the person who asked can decide it, and if the cluster changed in the meantime the card re-renders with what moved before letting you confirm anyway.
  • Work tickets from the thread - an escalated ticket’s thread reply carries Assign to me and, while a plan is awaiting a verdict, Approve plan and Request changes.
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 - never the bot’s.

​
If something does not work

For alert cards in Teams without the bot, use a webhook destination with the Adaptive Card template instead - see Microsoft Teams webhooks.

​
Source Control

Connect GitHub (via the Ankra GitHub App) or GitLab so the AI can read repositories, comment on pull requests, and power PR preview environments.

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