Revoking connections and keeping tokens safe
How to store agent tokens safely, switch connections off or remove them, and what to do if a token leaks.
An agent token is as powerful as the owner or admin who made it: anyone holding it can read and change your workspace through the MCP server (within the safety rules). Treat tokens like passwords.
Keeping tokens safe
- One connection per person and device, with a name that says so ("Claude Desktop, Sam's laptop"). Then you can remove one without affecting the others, and the audit log shows which was used.
- Keep tokens out of files you share or commit. In Claude Code and Cursor, read the token from an environment variable (
OPSDASH_MCP_TOKEN), as in Connecting Claude Code. In Claude Desktop the token sits in your own config file: don't share it. - Never paste a token into a chat, an email, a ticket, a task or a document. OpsDash only shows a token once, so there's never a reason to send it on.
- Don't reuse a token for several assistants.
Switch off or remove a connection
In Settings › Agents (owners and admins):
- Switch a connection Off to stop it at once without losing it; switch it On again later.
- Remove deletes it for good.
Last used on each connection helps you spot ones nobody uses any more. Remove them.
If a token leaks
- Remove that connection in Settings › Agents straight away. The token stops working immediately.
- Check the audit log for changes made with that connection.
- Make a new connection for whoever needs it, and store the new token safely.
When someone leaves
Connections stop working when the person who made them is no longer an owner or admin of the workspace. Still, remove their connections when you remove them from the team, so nothing is left lying around.
Clients' tokens
Client assistant tokens expire on their own (after 30 days, 90 days or a year). You can Revoke any of them on the client's Client settings › Their AI assistants, and switching off Let clients connect their own AI assistant in Settings › Client portal stops every client token at once. See clients' AI assistants.
Settings in OpsDash
These open in OpsDash. You’ll be asked to sign in first if you aren’t already.
Related articles
- Creating a staff connectionMake a connection and token in Settings › Agents for an AI assistant to use OpsDash's MCP server, and manage the connections you have.
- Connecting Claude CodeAdd OpsDash to Claude Code with a .mcp.json file that reads your token from an environment variable, so the token never goes in your code.
- Clients' AI assistantsLet a client's portal admins connect their own AI assistant, limited to what they can see and do in their portal, and see or revoke their tokens.