Review Security Sessions

Use the sessions page to understand the current browser security context and active session state.

Best for Human member Updated April 3, 2026

Web In this interface

4 steps Steps

1 interfaces Available in

Use this path when

The sessions page is for browser or session review, not for shared automation credentials.

What you'll finish here

Where this happens

Label	Value	Notes
Route	/workspace/settings/security/sessions	Security sessions route.

1. Open `/workspace/settings/security/sessions` from the security settings shell.
2. Review the visible session information and current authentication context.
3. Decide whether the next step is session review only or whether you actually need a personal API key instead.
4. Switch to the PAT guides only if the user now needs a CLI or script credential.

Stay in the same interface and move to the next closest task in this topic when needed.

Review the current personal API keys before creating a new one or revoking an old one.

Create a human-owned API key with the narrowest useful scope set and store it safely because the raw token is only shown once.

Revoke a human-owned API key by credential id when it is obsolete, leaked, or no longer appropriate for the workflow.

These guides stay close to the current workflow so you can keep moving without restarting discovery.

Create a human-owned API key with the narrowest useful scope set and store it safely because the raw token is only shown once.