> 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/token-lifecycle-states.md).

# Token lifecycle states

The states an e6data access token moves through - active, expired, and revoked - and how each is enforced.

An access token (PAT or service account key) moves through a small set of states.

| State       | Meaning                       | Authenticates?            |
| ----------- | ----------------------------- | ------------------------- |
| **Active**  | Created and within its expiry | Yes                       |
| **Expired** | Past its expiry timestamp     | No - returns `401`        |
| **Revoked** | Explicitly deleted            | No - rejected immediately |

* A token is **created** with its secret shown once; from then it is **active**.
* Expiry is enforced on **every** request. An expired token returns `401 Unauthorized` and **cannot be extended** - create a replacement and revoke the old one.
* Revocation takes effect **immediately** - a revoked token fails on its next request.

Note that a valid token whose owner lacks the required permission still returns `403 Forbidden` - that's an authorization result, not a token state. Removing a user's workspace access does **not** revoke their tokens; revoke them explicitly. 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)
* [Create, use, rotate, and revoke tokens](/query-engine/guides/security/access-tokens/create-use-rotate-revoke.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/token-lifecycle-states.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.