Tokens and access

The Tokens page lists each identity, authentication source, role, status, and creation time.

Create a token

1. Enter a descriptive person or automation name.
2. Enable admin only when the identity needs admin-panel access.
3. Choose create token.
4. Copy the token immediately; it is shown once.
5. Send it through a private channel.

Use distinct names for CI systems and human users. Avoid shared team tokens; they make revocation and the activity trail less useful.

Revoke access

Choose revoke all next to an identity. Revocation takes effect immediately and invalidates all tokens held under that name across every machine. Existing admin sessions under the name are also signed out.

Perforce-issued tokens display their source and expiry. Manually created tokens remain active until revoked.