Skip to main content
Some settings belong to you rather than to an organisation: where Ankra emails you, how you sign in, the accounts you connect, how you are notified, the tokens your scripts and editor use, and how the portal looks. They follow you across every organisation you belong to.

Open your account

Click your name at the foot of the sidebar to open the account menu. It holds:
  • Profile, which opens your account pages (/next/account).
  • Appearance: System, Light or Dark.
  • Show technical details, which opens every Details section and shows identifiers and exact values.
  • Support and Sign out.
Your account has eight pages, listed in its menu: Profile, Organisations, Invitations, Sign-in and security, Connected accounts, Notifications, API access and Preferences.

Profile

Profile (/next/account) has these sections:
  • About you: your name, email and picture. They come from the way you sign in; change them there, and Ankra shows the new ones the next time you sign in.
  • Contact email: where Ankra sends alerts and invoices, when your sign-in address is not the inbox you read. Enter the address, then the 6-digit code Ankra mails to it. The address is used once you enter the code.
  • Language: the language the portal is shown in.
  • Delete your account: revokes your tokens, removes your sign-in, your personal AI keys and your connected GitHub account, and takes you out of every organisation. If you are the only owner of an organisation other people belong to, Ankra refuses until you give someone else the owner role there. An organisation where you are the only member is not deleted with your account: it stays, with its clusters and its plan and nobody left to manage it, so delete it first. Click Delete account, type your email to confirm, then click Delete my account.
Deleting your account cannot be undone.

Organisations

Organisations (/next/account/organisations) lists every organisation you belong to and your role in each. The one you are in is marked You are here and links to its Organisation settings; Switch moves you to another. When the list is long, a search field finds an organisation by name or ID. To create one, click New organisation, enter a Name and click Create organisation. You become its owner and Ankra opens it; your other organisations stay as they are. The CLI does the same with ankra org list, ankra org switch <organisation> and ankra org create <name>: see ankra org.

Invitations

Invitations (/next/account/invitations) lists the organisations that invited you. Join takes you in. Decline asks Decline the invitation to <organisation>?; the invitation is removed, and to join later someone in that organisation has to invite you again.

Sign-in and security

Sign-in and security (/next/account/security) holds Ways to sign in, Two-step sign-in (passkeys and an authenticator app) and Recovery codes. See Account security.

Connected accounts

Connected accounts (/next/account/connections) links your own GitHub or Bitbucket Cloud account (Code), your Slack or Microsoft Teams identity (Chat), and your own AI keys. See Connected accounts and Your own AI keys.

Notifications

Notifications (/next/account/notifications) sets how you are notified:
  • Email: one switch per kind of email, sent to your contact email or, without one, the address you sign in with. The kinds that are always sent are listed under the switches.
  • Chat: Message me in Slack when an answer is ready and Message me in Teams when an answer is ready, for when you ask Ankra something long. Link Slack or Microsoft Teams in Connected accounts first.
  • Phone and tablet: the devices that get alerts on the lock screen from the Ankra app.
Which alerts go where for the whole organisation is set separately: see Notification routing.

API access

API access (/next/account/api) holds your personal tokens for the CLI, scripts, CI and the MCP server. A token acts as you: whoever has it can do what it allows, until it expires or you revoke it. The portal offers Create token only once your account has two-step sign-in. Without it, the page shows Add a second step to sign in first with a link, Set up two-step sign-in.
1

Create the token

Click Create token. Enter a Name that says where it will be used.
2

Choose what it can do

Under What can it do? pick one:
3

Choose when it expires

Under Expires after pick 7 days, 30 days, 90 days (the default) or 1 year. The field shows the date it stops working.
4

Copy the secret

Click Create token. The secret is masked until you reveal it and is not shown again after you close the dialog. The token now appears under Your tokens.
Renew on a token that is not revoked gives it a new secret, shown once, and says when the old one stops working; it is the main action on a token that expires soon. A token’s options menu offers Revoke and Revoke and remove. Connect your editor gives the set-up for Claude Code and Cursor: Claude Code signs in on its own, so it needs no token. See API tokens for what each access level allows.

Preferences

Preferences (/next/account/preferences) holds:
  • Appearance: the Theme, saved on your account. The account menu’s Appearance items set the same choice. Show technical details is here too.
  • Money: Show costs in chooses the currency Ankra shows costs in. Invoices stay in your organisation’s billing currency.
  • Ankra AI: When you ask Ankra to do something sets the mode a new conversation starts in. Ask investigates and explains, and never changes what is running. Plan proposes a plan for you to approve before it changes anything. Agent does the work, and asks before each change to a cluster.
  • What Ankra may do without asking you: the actions you approved once and told Ankra to repeat. Remove one and Ankra asks again next time.
See AI Assistant for how the modes work in chat.

Next step

Create a token and sign in with the CLI, or use the command palette and keyboard shortcuts to move around faster.