Secure your token
Store PATs safely and limit the damage if one leaks.
A Personal Access Token is a bearer credential. Anyone or any service that gets it can use it until it expires or you revoke it.
Store it safely
- Use a secrets manager or an environment variable in your deployment.
- Do not paste tokens into source code.
- Do not commit tokens to Git.
- Do not send tokens in chat, screenshots, or support tickets.
Reduce risk
- Choose as few scopes as you can.
- Use a short expiry for experiments.
- Create a separate token for each app or environment.
- Revoke tokens you no longer use.
If a token leaks
Revoke immediately
Open Settings → API Tokens and revoke the exposed token.Replace it where it is used
Remove the old value from every deployment, secret store, and local environment.
Create a replacement
Give it only the scopes the app really needs.
Revoke a token
Revoking a token takes effect immediately and cannot be undone.
Revoke flow
Open API Tokens
Go to Settings → API Tokens.Find the token
Use the name, prefix, workspace, expiry, and last-used columns to find the right one.
Click Revoke
Confirm the warning. Any outside app using the token stops working right away.
When to revoke
- The token leaked.
- The outside app is no longer in use.
- You need different scopes.
- A teammate or vendor no longer needs access.
- The token was created in the wrong workspace.
After revoking
If the automation still needs access, create a new token and update the outside app's configuration.
Team tokens
A token created in a team workspace belongs to that team. Keep team tokens separate from personal automation.