Create a Personal Access Token
Create a human-owned API key with the narrowest useful scope set and store it safely because the raw token is only shown once.
The browser PAT page explains scope meaning clearly before the key is issued.
- Choose scopes deliberately.
- Copy the raw token immediately.
- Use PATs only for human-owned automation.
Where this happens
Same Task, Other Interfaces
Use the version that matches where you are working now. The subject matter stays the same; the delivery changes by surface.
Keep this boundary clear
- PATs belong to a human and never exceed the human role. They are not workspace-shared automation credentials.
Do the work
- 1. Open the PAT page and start the create flow.
- 2. Choose a label, expiry, and only the scopes the workflow truly needs.
- 3. Create the key and copy the raw token immediately because the page only shows it once.
- 4. Store the token in the tool that will use it and never expect the browser to reveal it again later.
Keep Going in Sessions and Personal Tokens
Stay in the same interface and move to the next closest task in this topic when needed.
Review Security Sessions
Use the sessions page to understand the current browser security context and active session state.
List Personal Access Tokens
Review the current personal API keys before creating a new one or revoking an old one.
Revoke a Personal Access Token
Revoke a human-owned API key by credential id when it is obsolete, leaked, or no longer appropriate for the workflow.
Nearby Guides
These guides stay close to the current workflow so you can keep moving without restarting discovery.