> For the complete documentation index, see [llms.txt](https://docs.e6data.com/query-engine/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.e6data.com/query-engine/reference/token-reference/personal-access-token.md).

# Personal access token

The structure of an e6data personal access token (PAT) and how it's stored.

A personal access token (PAT) is a four-part, underscore-separated string carrying a human user's identity.

```
e6pat_<workspace>_<keyId>_<secret>
```

| Segment       | Meaning                                                                       |
| ------------- | ----------------------------------------------------------------------------- |
| `e6pat_`      | The PAT prefix - checked before any lookup; a value without it is rejected    |
| `<workspace>` | The workspace the token is scoped to - it is not valid in any other workspace |
| `<keyId>`     | An identifier for the key                                                     |
| `<secret>`    | The secret material you must protect                                          |

* The full value is **shown once**, at creation - only its prefix is stored or shown afterward.
* The token is **workspace-scoped** and carries identity only; what it can do comes from the user's role bindings, not the token itself.

The other credential prefix is `e6sa_` (service account key). See the canonical [token-types table](/query-engine/guides/security/access-tokens.md#token-types).

## See also

* [Service account key format](/query-engine/reference/token-reference/service-account-key-format.md)
* [Token lifecycle states](/query-engine/reference/token-reference/token-lifecycle-states.md)
* [Token expiry rules](/query-engine/reference/token-reference/token-expiry-rules.md)
* [Access tokens](/query-engine/guides/security/access-tokens.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.e6data.com/query-engine/reference/token-reference/personal-access-token.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.