> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ankra.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect your Git provider and your own accounts

> Tell your organisation's Git connection apart from your own, then link your GitHub, Bitbucket Cloud, Slack, Teams and AI keys to your account.

Two kinds of connection reach your code and your chat. The **organisation's** connection to GitHub, GitLab or Bitbucket Cloud is made once, by an admin, and is what clusters, applications and pipelines use. **Your own** connected accounts belong to you: they credit you for what Ankra pushes, let Ankra reach Bitbucket repositories with your access, tell Ankra who you are in Slack or Teams, and hold your own AI keys. This guide connects your own accounts; it takes a few minutes.

## Before you start

* Your organisation's Git provider is connected. Which host supports what, and how each is connected, is in [Git providers](https://docs.ankra.ai/integrations/git-providers.md): [GitHub](https://docs.ankra.ai/integrations/github.md), [GitLab](https://docs.ankra.ai/integrations/gitlab.md), [Bitbucket Cloud](https://docs.ankra.ai/integrations/bitbucket-cloud.md).
* For chat, the organisation has the Ankra app in Slack or Microsoft Teams, set up in **Ankra AI → Gateway connections**: see [AI connections](https://docs.ankra.ai/platform/ai-connections.md).

## Open Connected accounts

Click your name at the foot of the sidebar, choose **Profile**, then **Connected accounts** (`/next/account/connections`). The page has two sections, **Code** and **Chat**, and **Your AI keys** under them.

**1. Connect GitHub**

Under **Code**, the **GitHub** row reads **Not connected. Connect it so commits Ankra pushes are attributed to you.** Where the row offers **Verify with GitHub**, click it and approve the request at GitHub. Back in Ankra the page reads **Your GitHub login is verified.**, and the row shows how the login was found: **Verified with GitHub**, **From your GitHub sign-in**, **From installing the Ankra GitHub app** or **Entered by you**.

Without **Verify with GitHub**, or if you would rather not verify, choose **Enter it yourself**, type your **GitHub login** and click **Save**; Ankra checks the login exists on GitHub before saving it. To change it later, open the row's options menu and choose **Enter a different login**; **Verify again** checks a login you entered.

**2. Connect Bitbucket Cloud, if your code lives there**

The **Bitbucket Cloud** row reads **Not connected. Needed only if your code lives on Bitbucket.** Click **Connect** and approve the access at Bitbucket. The page reads **Bitbucket Cloud is connected as `<login>`.**, and the row says **Ankra reaches your Bitbucket repositories with your access.**

GitLab has no personal connection on this page.

**3. Link Slack or Microsoft Teams**

Under **Chat**, the **Slack** and **Microsoft Teams** rows read **Not linked** until you link them. You link from the chat app itself, through the Ankra app there, not from this page. Once linked, the row reads **Linked in `<workspace>`. Ankra knows it is you when you ask it there.**

To be told in chat when a long answer is ready, follow **Chat notifications** to **Your account → Notifications**: see [Your account](https://docs.ankra.ai/platform/user-profile.md#notifications).

**4. Add your own AI keys, if you want them**

**Your AI keys** holds your own Anthropic or OpenRouter API keys. Ankra runs your Ankra AI chats and the reviews of your pull requests on them, in the order you set. The steps are in [Your own AI keys](https://docs.ankra.ai/platform/personal-ai-keys.md).

## Verify

Open **Your account → Connected accounts** again. **GitHub** shows your login, **Bitbucket Cloud** shows the account it is connected as, and **Slack** or **Microsoft Teams** reads **Linked in** with your workspace or tenant.

## Disconnect

Open the row's options menu and choose **Disconnect**:

* **Disconnect GitHub?**: commits Ankra pushes for you are no longer attributed to you. You can connect it again later.
* **Disconnect Bitbucket Cloud?**: Ankra stops reaching your Bitbucket repositories with your access. You can connect it again later.

A Bitbucket Cloud connection that stopped working offers **Reconnect**.

## What can go wrong

| What you see | What it means |
| - | - |
| **GitHub was not verified: the request was declined at GitHub.** | You declined the request at GitHub. Click **Verify with GitHub** again and approve it, or enter your login yourself. |
| **GitHub was not verified. Try again, or enter your login yourself.** | The verification did not finish. Try again, or use **Enter it yourself**. |
| **Bitbucket Cloud was not connected. Try again.** | The connection did not finish at Bitbucket. Click **Connect** again. |
| **Nothing was disconnected** | The disconnect failed; the message under it says why. The connection is as it was. |

## Next steps

* [Git providers](https://docs.ankra.ai/integrations/git-providers.md): what each Git host supports in Ankra.
* [Your own AI keys](https://docs.ankra.ai/platform/personal-ai-keys.md): add and order your Anthropic and OpenRouter keys.
* [Your account](https://docs.ankra.ai/platform/user-profile.md): every page of your account.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.