> 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/my-account/security-credentials.md).

# Security Credentials

**Security credentials** lists the security tokens that belong to you. Integrations such as the Code Analysis CLI, the IDE extension and AI assistants (MCP clients) use a token to act on your behalf, with the roles assigned to that token. Use a separate token for each integration, and review its roles, expiry and whether it should stay enabled.

Open it from **Administration** → **My Account** → **Security credentials** in the sidebar, or from the **Security credentials** tab of My Account.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FYX380wqaWQEZ5XfytHR9%2Fv2-account-security.png?alt=media&amp;token=93cc4f04-d271-4a4c-8c41-e3d78dc7780e" alt="Security credentials list with Generate Token, status filter and the credentials table"><figcaption><p>Your security credentials</p></figcaption></figure>

{% hint style="info" %}
Only credential metadata is listed. A token's secret value is shown once, when you generate it, and never again. Tokens for other users are managed in [Access Tokens](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/organizations/access-tokens.md).
{% endhint %}

## Credentials List

| Control                              | What it does                                       |
| ------------------------------------ | -------------------------------------------------- |
| **Status**                           | **All**, **Enabled**, **Expired** or **Disabled**. |
| **Saved filters** / **Save filters** | Re-apply or save the current filters.              |
| **Search your credentials**          | Finds a credential by name.                        |
| **Refresh**                          | Reloads the list.                                  |
| **Columns**                          | Shows or hides columns.                            |
| **Export**                           | Downloads the list.                                |

| Column         | Description                                                                                                |
| -------------- | ---------------------------------------------------------------------------------------------------------- |
| **Credential** | The token's name.                                                                                          |
| **Status**     | **Active**, **Disabled**, or **Expired** once its expiry date has passed.                                  |
| **Roles**      | The roles assigned to the token. When there are more than two, hover over the extra count to see the rest. |
| **Expires**    | The expiry date, or **No expiry configured**.                                                              |
| **Manage**     | **Disable credential** or **Enable credential**.                                                           |

## Generate a Token

1. Click **Generate Token**.
2. In **Generate New Token**, enter the **Token Name**. **Required.**
3. Optionally, choose an **Expiry** date. Leave it empty if the token is not intended to expire.
4. On the **Roles** tab, under **Assign Roles**, select the roles the token gets. Use **Search Role** to find one.
5. Click **Save changes**.
6. On **Token Generated**, copy the token and store it safely.

{% hint style="danger" %}
Copy the token straight away: it is not shown again. Treat it like a password, and give it only the roles the integration needs.
{% endhint %}

## Disable or Enable a Credential

1. Click **Disable credential** (or **Enable credential**) in the **Manage** column.
2. Read the confirmation and confirm.

| Action                 | Effect                                                            |
| ---------------------- | ----------------------------------------------------------------- |
| **Disable credential** | Integrations using this credential lose access.                   |
| **Enable credential**  | The credential regains its assigned access until its expiry date. |

## Next Steps

* [IDE Projects](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/my-account/ide-projects.md): see the projects you scanned in the IDE extension.
* [My Activity](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/my-account/my-activity.md): check what was done with your account.
* [MCP Integration](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/global-settings/mcp-integration.md): connect an AI assistant with a token.
* [My Account](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/my-account.md): back to the overview.


---

# 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/my-account/security-credentials.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.
