> 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/limits-and-quotas/token-limits.md).

# Token limits

Limits and recommended practices for e6data access tokens - expiry bounds and per-consumer scoping.

Limits and recommended practices that apply to access tokens (personal access tokens and service account keys).

| Limit                    | Value                                           |
| ------------------------ | ----------------------------------------------- |
| Expiry unit              | Days                                            |
| Default expiry           | 90 days                                         |
| Maximum expiry           | 3650 days                                       |
| Never-expires            | Allowed (only with a rotation process in place) |
| Visibility               | The secret is shown once at creation            |
| Keys per service account | No hard limit (rotate freely)                   |

## Recommended practices

* **One credential per consumer** - never share a token across apps or teams, so you can revoke one without breaking others.
* **Set an expiry and rotate** before it lapses, using create-before-delete.
* **Least privilege** - a token is exactly as powerful as the role bound to its owner; grant the minimum needed.

For the full guidance, see [Token security best practices](/query-engine/guides/security/access-tokens/token-security-best-practices.md).

## See also

* [Token expiry rules](/query-engine/reference/token-reference/token-expiry-rules.md)
* [Workspace limits](/query-engine/reference/limits-and-quotas/workspace-limits.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/limits-and-quotas/token-limits.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.