> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/organizations/access-tokens.md).

# Access Tokens

Access tokens let integrations, such as CI/CD pipelines, AI assistants and scripts, act as a person with a subset of that person's roles. This tab lists the tokens across your workspace. Only metadata is listed; a token's value is shown once, when it is created.

Open it from **Administration** → **Organizations** → **Access tokens** in the sidebar.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FdTvGspa1TbSuHDGsuM0S%2Fv2-org-tokens.png?alt=media&amp;token=47890aae-c62e-4878-9b49-eb893cb97efa" alt="Access tokens tab with status tiles, filters and the access token directory"><figcaption></figcaption></figure>

## Counts and Filters

| Tile                    | Description                                                 |
| ----------------------- | ----------------------------------------------------------- |
| **All tokens**          | Every token matching the current search and owner.          |
| **Enabled**             | Enabled tokens, including enabled tokens past their expiry. |
| **Expired**             | Tokens whose expiry date has passed.                        |
| **Expiring in 30 days** | Enabled tokens that stop working soon.                      |
| **Never expire**        | Enabled tokens with no expiry date.                         |

Click a tile to list those tokens.

| Filter      | Description                                                                                                                                                                   |
| ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Status**  | **All**, **Enabled**, **Expired**, **Expiring in 30 days**, **Never expire**, **Disabled**, or **Holds access-admin permissions** (tokens that can administer access itself). |
| **Acts as** | One or more token owners.                                                                                                                                                     |
| Search      | Finds tokens by name.                                                                                                                                                         |

**Saved filters** and **Save filters** keep a filter combination. **Refresh**, **Columns** and **Export** work as on other lists.

## Access Token Directory

| Column      | Description                                                                                             |
| ----------- | ------------------------------------------------------------------------------------------------------- |
| **Token**   | The token name and when it was created.                                                                 |
| **Status**  | **Active**, **Expired** or **Disabled**.                                                                |
| **Acts as** | The person the token acts as.                                                                           |
| **Roles**   | How many roles the token carries.                                                                       |
| **Expires** | The expiry date, or **Does not expire**.                                                                |
| **Manage**  | **Review token**, **Open owner** (opens the owner's details) and **Disable token** or **Enable token**. |

**Review token** opens the token drawer: status, **Acts as**, **Expires**, **Created**, **Token value** (**Not retrievable; only a digest is stored**) and **Roles carried by this token**. The token can never exceed the roles its owner holds.

## Create an Access Token

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FKAuXxTFVb7mLzdEbTzUY%2Fv2-org-tokens-create.png?alt=media&amp;token=fea477d7-2653-4c37-bd1c-0bb108af7298" alt="Create access token form with token name, acts as, roles and expiry"><figcaption></figcaption></figure>

1. Click **Create access token**.
2. Enter a **Token name**.
3. Choose who the token **Acts as**.
4. Choose the **Roles** the integration needs.
5. Optionally set **Expires on**.
6. Click **Create token**.
7. Copy the token value and keep it in a secret store.

| Field          | Description                                                                                                                                                                    |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Token name** | Required. Name it after the integration that will use it, for example "CI pipeline".                                                                                           |
| **Acts as**    | **Me**, or another person when your role can create tokens for others. The token acts as this person and can never hold a role they do not hold. Changing it clears the roles. |
| **Roles**      | Required; choose at least one. Choose only what the integration needs. Only roles the owner holds are offered.                                                                 |
| **Expires on** | Leave empty only for a token that must never expire; prefer an expiry date.                                                                                                    |

{% hint style="danger" %}
The token value is shown only once, under **Copy this token now**. Only a digest is stored, so the value cannot be shown again. If it is lost, create a new token. Keep tokens in a masked secret store and never paste them into files you commit.
{% endhint %}

## Disable or Enable a Token

1. Click **Disable token** (or **Enable token**) on the row.
2. Confirm in the drawer that opens.

Integrations using a disabled token lose access on their next request. You can enable it again later; it regains its roles until its expiry date.

{% hint style="warning" %}
You need a role that can generate access tokens to create one. You can disable or enable your own tokens; disabling other people's tokens needs a role that can manage people.
{% endhint %}

## Next Steps

* [Roles](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/organizations/roles.md): create narrow roles for pipelines and AI assistants.
* [Setup](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/setup.md): create a token and copy a ready-made pipeline or AI assistant configuration.
* [Users](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/organizations/users.md): disabling a person also disables their tokens.


---

# 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://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/organizations/access-tokens.md?ask=<question>&goal=<user_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.
