Preferences

Console settings and accessibility

Set your Archibot account preferences, link a second login, manage Git access and spending caps, and choose language, appearance, and accessibility from the Settings page.

Customer adminsCustomer membersPlatform operatorsPlatform admins

Last updated June 18, 2026

What Settings is for

Settings is the per-user home for your Archibot account preferences plus how Console looks and behaves for you. It does not change other users’ preferences, and appearance choices apply to the browser you are using.

Settings is organized into two top-level tabs:

• Archibot account — the default tab. It keeps account setup, Git access, API keys, CI and Review, support, activity, billing, and spending caps in Console instead of inside the Chat workspace.
• Browser and session — your Console identity, language and region, appearance, and accessibility for this browser.

Below both tabs, a Login methods panel lets you link a second email login to the same account.

If you are new to the Console layout, start with Welcome to Archibot and Access roles so the role-gated controls below make sense.

Archibot account tab

Settings opens on the Archibot account tab. A row of pills selects which surface you are looking at, and status badges plus a Refresh action sit just below them.

The pills, left to right, are:

The Billing and Spending caps pills only appear if you have customer admin or platform access. Everyone else sees the first six pills.

The status badges show whether Chat and API access are enabled and how many credits remain. Use Refresh if you have just changed plan or access and want the latest state without reloading the page.

Setup

Setup is where you confirm what the account is for before day-to-day use. It summarizes whether you are signed in, the account name, and billing status, then offers quick links to open Chat, manage keys, and open files. Lower on the panel you confirm your plan and intended use. For the full walkthrough, see ArchibotChat setup.

Git Access

The Git Access pill manages how Console connects to your Git provider for workspaces. Use it to confirm or refresh provider access without leaving Settings. For provider connection and SSO details, see ArchibotChat access and SSO.

API Keys

API keys are for external sessions outside managed workspaces. Managed Archibot workspaces provision their key automatically, so you only need a key here when you are calling the API from your own tooling. See ArchibotChat API keys for creating, rotating, and revoking keys.

Support and Activity

The Support pill opens a form to submit a support case from Console; the Activity pill shows recent account activity and an export action. See ArchibotChat support cases and ArchibotChat activity and audit.

Browser and session tab

Select Browser and session to manage your Console identity, language, appearance, and accessibility for this browser. These choices apply to the browser you are using and do not change anyone else’s view.

The tab is laid out as four areas:

• Console identity — your username, email, and role badges. Use it to confirm you are signed in as the expected account before account-scoped work.
• Access metrics — compact tiles for active access, customer scopes, Archibot readiness, and remaining credits.
• Language and region — choose the language used for Console and in-workspace guidance, with a note on supported countries and an expandable Archibot language coverage panel.
• Appearance — theme, motion, contrast, and focus.

Language and region

Choose the language used for Console and in-workspace guidance. When you have not chosen a language, the tenant default applies, so a new member sees a sensible language before making their own choice. Operators set the tenant default separately.

The Console language picker also appears in the left sidebar for a quick change. Below the picker, a note describes the supported countries and territories, and a Show language coverage disclosure lists per-locale status for browser chat, workspace chat, and the editor extension.

Appearance and accessibility

Appearance settings are the stable home for display preferences. The header theme toggle stays available for quick changes.

Motion, contrast, and focus are accessibility controls. Set Motion to Reduced and Focus to Strong if you rely on the keyboard or are sensitive to animation. A small help button next to Appearance explains the options inline.

Spending caps

The Spending caps pill on the Archibot account tab sets monthly limits for each billable Console feature. It only appears, and is only editable, for users with customer admin or platform access. Others see an access-required notice.

Caps are organized in two scopes:

• Customer defaults apply to everyone in the customer account before any override.
• User overrides set tighter or looser caps for a single user while preserving the customer default policy.

To edit caps:

1. Select Spending caps from the Archibot account pills.
2. In Customer account, choose or type the customer you are editing. Known customers appear as suggestions.
3. Optionally narrow the tables with Search analytics and the Billable service filter.
4. Edit a row in Customer defaults: set the monthly spend cap, monthly usage cap, cap action (Alert only, Block new work, or Disabled), and state (Active or Paused).
5. For a single user, type or pick a name under User, then edit the matching row in User overrides.

Each row saves on its own once you change a value. Use Refresh to reload the latest caps and recent usage.

Caps are accounting limits, not credentials. Never put payment data or secrets in a cap note. For how caps relate to credits and invoices, see Usage and billing and ArchibotChat billing and credits.

Login methods

Below both tabs, the Login methods panel links another email-based login to the same account without leaving Settings. While signed in:

1. Open Login methods if it is collapsed.
2. Enter the secondary email and choose Send code.
3. Enter the one-time code and choose Link email.

A confirmation message names the email and the customer it is linked to. Secondary logins reach the same account scopes. They are not a way to share one account between people.

What stays out of Settings

Settings is for preferences and your own account. It does not expose service tokens, Kubernetes access, internal service addresses, or other customers’ data. Keep secrets out of any note, support text, or export request you start here. If you hit an error you cannot resolve, see Troubleshooting or open a case from the Support handoff guide.