Skip to main content
Some settings belong to you rather than to an organisation: where Ankra emails you, how you sign in, whether the portal is dark or light, how you are notified, and the tokens your scripts and editor use. They live in your profile and follow you across every organisation you belong to. Open the profile menu in the sidebar and select Profile. The profile sidebar has five tabs.

​
General

  • Account - your name, email and picture, taken from your sign-in provider. Change them there.
  • Contact email - where Ankra sends account, invitation and notification emails, if that should differ from your sign-in address (for example when you sign in with an Apple private relay address).
  • GitHub Connection and Bitbucket Cloud Connection - link your own GitHub or Bitbucket identity so commits Ankra pushes on your behalf are attributed to you.
  • AI Assistant - personal AI preferences (tips, auto-approved actions, model and interaction mode) are set in the AI chat panel: Open AI chat, then the settings (gear) icon. See AI Assistant.
  • Delete account - permanently deletes your account and personal data.

​
Authentication

Two-factor authentication: authenticator apps, passkeys and recovery codes. See Account Security & 2FA.

​
Appearance

Choose Light, Dark or System (follow your operating system). The choice is saved to your account. The profile menu also has a one-click toggle that cycles through the three modes.

​
Notifications

  • Email Subscriptions - choose which emails you receive from Ankra: product updates, platform announcements, and scheduled maintenance and incident notices.
  • Chat completion notifications - get a Slack or Microsoft Teams message when an AI chat task finishes. The Slack or Teams connection itself is set up in your organisation’s Integrations settings.
  • Push notifications - the mobile devices your notifications are pushed to. Send a test notification or remove a device.
Which alerts go where for the whole organisation is configured separately, in Notification routing.

​
API Tokens

Create and revoke personal API tokens for the CLI, scripts and the MCP server. Create asks for a name and, optionally, MCP access; the token is shown once, so copy it before closing the dialog. The page also gives ready-made MCP set-up for Claude Code and Cursor. See API tokens for scopes.

​
Next step

Create an API token and log in with the CLI, or use the command palette and keyboard shortcuts to move around faster.