Skip to content

Manage Personal Access Tokens

For Access Tokens, you can:

  • Create a token to use for the CLI, or an AI assistant.
  • Revoke or delete a token you no longer need.

Create a Personal Access Token

Prerequisites

  • A vHaaS account

Steps

1. Open your personal access tokens

Select the Profile Menu in the navigation bar and open its Personal Access Tokens tab.

2. Create the token

Open the dialog with Create Access Token and set a name and an expiration date.

Copy the token now

Copy and store the access token in a secure location. You will not be able to view the token again after you leave or refresh the page.

Revoke or delete a Personal Access Token

Prerequisites

  • An existing personal access token of your own

Steps

1. Open your personal access tokens

Select the Profile Menu in the navigation bar and open its Personal Access Tokens tab.

2. Revoke or delete the token

Both actions sit directly in the token's row:
  • Revoke: the slider. This disables the token and cannot be undone.
  • Delete: the trashcan icon. Note that once a token is deleted, it cannot be recovered.

Troubleshooting

Symptom Likely cause Solution
API or CLI request fails with 401 No valid token was sent — the private-token header is missing, or VEHAAS_TOKEN is not set Set VEHAAS_TOKEN or pass --token; see [Authentication].
Requests fail with 401 although the token is still listed in the table The token has expired or was revoked. Note that the Status column shows Revoked for expired tokens too, and that revoking cannot be undone Compare Status against the expiration date and create a new token.
Requests keep succeeding for up to a minute after the expiration date has passed Token lookups are cached briefly, and expiry is only re-evaluated once the cache entry ages out Wait a moment. Revoking or deleting a token through the UI takes effect immediately.
A token that worked before loses access to an assembly The token mirrors your permissions, so losing a group membership or a role removes that access from the token as well Check your group membership and role; see [Organization and visibility structure].
The token name is rejected when you create it Token names must be unique among your own personal access tokens Choose a different name.
The token value is no longer visible anywhere The value is shown only once, in the dialog directly after creation Create a new token and store the value in a secure location.
Your token does not appear in the Access Tokens tab of a group or organization Personal access tokens live in the Profile Menu only. Nobody else sees them — not even organization admins Open the Personal Access Tokens tab in the Profile Menu. The group and organization tabs list scoped tokens only.
The token has no Environment Variables or Version Control Access tab Both settings belong to scoped tokens. Sessions started with a personal access token use the settings of your own account Configure them in your [user profile].