Admin Key
Every agent can have an Admin Key — a secret that unlocks admin-level debug commands inside a chat session. This page explains what it's for and where to manage it now that it has moved out of the agent's own Availability page.
Who can manage the Admin Key? Only Owner and Admin, at the organization level.
What the Admin Key is for
The Admin Key is an operational, support-oriented credential — not an access-control setting. Whoever knows it can type debug commands into a live chat session (for example, to inspect the conversation's raw context) without those commands being treated as normal user input.
It has nothing to do with who is allowed to chat with the agent — that's what Availability and Required Login control instead.
Why this moved to Organization
The Admin Key used to live on the agent's own Availability page, next to Required Login. Bundling it there mixed two different concerns: Availability is about who may enter a conversation, while the Admin Key is a support credential. Splitting them makes Availability a cleaner "who can access this agent" page, and puts the credential where operational/support responsibility already sits — with the organization's Admins and Owners.
Where to find it
Open the Organization page → click your organization → open the Agents tab → on the agent's card, click Manage Admin Key.
Managing the key
From the Admin Key panel you can:
| Action | What it does |
|---|---|
| Set / Update | Enter a new key value and save it. |
| View | Reveal the current key value (masked by default). |
| Clear | Remove the key entirely, disabling admin debug commands for this agent until a new one is set. |
Treat the Admin Key like any other credential: share it only with people who need it for support, and rotate it if you suspect it has leaked.
Next step
Return to Agents in an Organization to manage agents, or see Deleting an Agent for the other action that moved here.