> For the complete documentation index, see [llms.txt](https://docs.probe.splx.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.probe.splx.ai/settings/platform-settings/user-settings/personal-access-tokens.md).
# Personal Access Tokens
Generated access tokens **inherit the same feature and workspace permissions as the user** who creates them, and these permissions apply when accessing the platform through the API.
## Access Token Generation
1. Click the “Generate New Token +” button.
2. Provide Token Details.
1. Token Name: Assign a meaningful name to your token.
2. Description: Add a brief description for clarity.
3. Duration: Specify the token’s expiration period.
{% hint style="warning" %}
Once generated, the token will be displayed only once. Be sure to copy and securely store it immediately, as it cannot be accessed again.
{% endhint %}
Figure 2: Generation of a New Token
## Managing Your Tokens
On the **Personal Access Tokens page,** the tokens table lists all previously created tokens with the following details:
* Name
* Partial Token Key (not the full key, for security reasons)
* Created Date
* Expiration Date
* Delete Token Option
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.probe.splx.ai/settings/platform-settings/user-settings/personal-access-tokens.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
