Your organization's AI key

Every AI feature of AutoTestX (Write with AI, AI diagnosis and AI healing) runs on one Anthropic key per organization. An organization admin chooses which one in Organization → Settings, in the AI key card.

Choice	AI runs on	Counts against the plan’s AI allowance
Our own Anthropic key	Your organization’s Anthropic account	No. Usage is still listed, as paid by your organization’s key
The AutoTestX key (the default, except on Enterprise)	AutoTestX’s Anthropic account	Yes
Turn AI off	Nothing	–

On the Enterprise plan, AI runs only on your own key. The AutoTestX key cannot be chosen. Until a key is saved, AI features are inactive and say why.

Saving the key

1. In Organization → Settings, in AI key, choose Change.
2. Choose Our own Anthropic key, paste the key and, only for a key that is not scoped to one workspace, the workspace id (wrkspc_…).
3. Save, then Test connection: one tiny request that says whether the key works, or why not (The key was rejected, The workspace does not exist).

The key is stored encrypted. After saving, only its last four characters are shown, and no page, API or export ever returns it. To rotate it, paste the new key; to keep the key and change only the workspace, leave the key field empty. Choosing the AutoTestX key or turning AI off removes the saved key: to go back, paste it again. Changes are written to the audit log without the key.

When the key stops working

When Anthropic refuses the key (revoked, no credit left, no permission), AI stops for the organization:

• Write with AI is disabled and says why. AI diagnosis records AI stopped: Anthropic rejected your organization’s key. Healing uses tiers 0 and 1 only.
• It is never switched to the AutoTestX key by itself. Your organization may not allow its page content to reach another AI account, and only your admins know. On a plan other than Enterprise, an admin may choose The AutoTestX key in the card: a saved, audited choice, not a fallback.
• At most one trial request an hour checks whether the key works again (a quota that reset). A successful Test connection, or a new key, clears it at once.
• A timeout, a busy service or a server error is not the key’s fault: it fails only that one request.

Runs, tiers 0 and 1, failure classes and CI results are never affected.

Who is told

State	Organization admins see	Email to organization admins
Enterprise, no key	A warning banner on Organization → Projects and Settings, and the card	When the organization starts on Enterprise or moves to it
The key is failing	A warning banner, and the card with the error and when it was last tried	When it starts failing
Another plan, the AutoTestX key	An information banner they can dismiss; the card always says it	Once, when the organization starts using it
AI turned off	The card	No

Everyone else sees the reason on the feature they tried, with Ask your Org Admin.

Plan changes

The organization moves	With its own key	Without one
To Enterprise	Nothing changes	AI becomes inactive until a key is saved
From Enterprise to another plan	Nothing changes	AI stays off until an admin adds a key or chooses the AutoTestX key: the organization never sent its data to AutoTestX’s account, so it does not start to by itself
To a smaller AI allowance	Nothing changes	The smaller allowance applies

For whoever runs the server

Keys are encrypted with ATX_ENCRYPTION_KEY (32 bytes: 64 hex characters, or base64). Set it before anyone saves a key, and keep it with your other secrets, not in the data folder:

openssl rand -hex 32

Without it the card says the server cannot store keys and refuses to take one. Losing or changing it makes every saved key unreadable: those organizations’ AI stops with the server cannot read the saved key, and their admins must save the key again. See Configuration.