Personal Access Tokens
Platform
Text size
Personal Access Tokens
Tokens let external tools and scripts authenticate as you via the API. Keep them secret and treat them like passwords.
Open the profile avatar menu, then click Personal Access Tokens. You can also open the page from workspace settings when that route is enabled for your tenant.
Catalog
The page lists tokens you already created. Each row shows metadata such as name and dates. The secret itself is never shown again after you close the reveal step.
Generate a new token
- Click Generate new token.
- Dialog title: Generate new token.
- Fill the form:
| Field | Required | Example |
|---|---|---|
| Token name | Yes | docs-capture-ci-pipeline (placeholder: CI pipeline token) |
| Expiration | Yes | 30 days (options: 1 day, 7 days, 30 days, 60 days, 90 days, 180 days, 1 year, or Custom) |
| Description | Yes | Docs capture token for CI examples. |
- Enter a recognizable Token name.
- Choose an Expiration preset (or Custom for a specific date).
- Enter a Description of what the token is for.
- Click Generate token to create it, or Cancel / Close to discard.
Copy the secret once
After generation, a reveal step shows the token secret.
- Copy the token immediately and store it in a secure secret store.
- Confirm you have copied it (for example I've copied the token) before closing.
- You cannot view the secret again later. If you lose it, regenerate or create a new token.
tip
Keep tokens secret. Do not commit them to source control or share them in chat.
Manage an existing token
From the row Actions menu:
| Action | What it does |
|---|---|
| Regenerate | Issues a new secret for the same token. The old secret stops working. Copy the new value from the reveal step. |
| Delete | Removes the token permanently. Scripts using it fail until you create a replacement. |
Use short-lived tokens for CI when you can, and delete tokens you no longer need.