Skip to Content
OpenInspect
Administration

Govern access tokens

Turn personal access tokens off, cap their lifetime, limit the permissions they may hold, and revoke any member's tokens.

Last reviewed View as MarkdownEdit on GitHubGive feedback

Members issue personal access tokens to let tools such as the MCP server call OpenInspect as them. Settings › Access token policy lets you set the rules every token follows, and revoke any member's tokens.

You need the Manage personal access tokens permission (workspace.personal_access_tokens.manage). Owners and Administrators have it; you can add it to a custom role, for example a security reviewer's, without granting member management.

The policy

The policy applies to existing tokens the moment you save it, not only to new ones:

SettingEffect
Allow personal access tokensOff refuses every token at once and stops members creating new ones. Tokens are not revoked: turning it back on restores them.
Longest lifetimeTokens older than this stop working, even if they were issued for longer. New tokens cannot be issued for longer.
Permissions tokens may holdNarrows every token's grant to these permissions, and new tokens cannot be granted others. Workspace administration permissions are never available. Allowing Manage skills also allows Read skills, which a token needs to use it.

Turning tokens off is the fastest response to a suspected leak when you do not know which token leaked. Every policy change is recorded in the audit log with the settings before and after, and saving refuses to overwrite a change someone else made since you loaded the page.

Members' tokens

The same page lists every member's tokens, newest first, with each token's owner, permissions, last use, and expiry. It never shows a token's value; OpenInspect stores only a hash.

  • Revoke stops one token immediately.
  • Revoke all of a member's tokens stops every token that member holds, for example when a laptop is lost. It checks again until no token is left, so tokens created while it runs are revoked too, but one created after its last check is not. If someone may still be creating tokens as the member, suspend the member first.

Revocations are recorded in the audit log with you as the actor and the member as the target. A member's tokens are also refused while the member is suspended, and deleted with the member's account.

On this page