Personal Access Tokens

BETA

Agent Gateway is in BETA, and we're continuing to expand its capabilities. Your feedback helps shape what we build next—reach out to us through Relewise Support.

Personal Access Tokens authenticate Agent Gateway requests with your My Relewise user identity.

Use a Personal Access Token instead of sharing API Keys with AI assistants, automation tools, or external apps.

Create a Token

In My Relewise, open User > Personal Access Tokens, then select Create New Token. On the Agent Gateway page, you can also select Create Token to create a token for the active Dataset, Manage All Tokens to open the token overview, or Manage Token beside a listed token to manage it directly.

When you create a token, My Relewise shows the token value once. Store it immediately in the connected tool or secret store. You cannot retrieve the same token value later.

Token Status

My Relewise groups tokens by status:

Status	What It Means
Active	The token can authenticate requests when all Agent Gateway authorization checks pass.
Expired	The expiration date has passed, so the token can no longer authenticate requests.
Revoked	The token has been permanently disabled.

The Agent Gateway page for a Dataset shows non-revoked tokens whose Dataset Scope includes that Dataset. Expired tokens remain in this list so you can identify and replace them. Use the full Personal Access Token overview to find revoked tokens.

Expiration

A token can have an expiration date or Never expires. After it expires, Agent Gateway rejects requests that use it.

Expired tokens remain visible so you can audit what existed, but they cannot be used for new requests.

Regenerate a Token

Regenerating a token, also called rotating it, creates a new token value for the same Personal Access Token record.

Use regeneration when a token value is lost or may have been exposed. After regeneration, update the connected tool with the new value. The old value stops working.

Revoke a Token

Revoking a token disables it permanently. Use revoke when the token is no longer needed or should no longer be trusted.

Revoked tokens remain visible in My Relewise for audit history.

Dataset Scope

Dataset Scope controls which Datasets the token can be used with.

Dataset Scope	What It Means
No Datasets	Blocks the token from all Datasets.
All Datasets	Allows all current and future Datasets available to your user.
Selected Datasets	Allows only the Datasets selected in My Relewise.

Dataset Scope does not override the Agent Gateway Configuration or your user permissions. Agent Gateway still checks those gates for every request.

Last Used

My Relewise records when a token was last used. A token that has not been used shows Never used. Use this value to identify unused tokens and decide whether they should be revoked.