> For the complete documentation index, see [llms.txt](https://docs.chassy.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chassy.io/operator-guides/generate-chassy-tokens.md).

# Generate Chassy Tokens

Chassy's GitHub actions require that you provide a Chassy token for authentication. This guide will get you up and running with the generation of Chassy tokens.

{% embed url="<https://youtu.be/3LFd866TpFk?feature=shared>" %}
Video tutorial alternative
{% endembed %}

{% hint style="info" %}
Only an Admin or Manager is allowed to generate Chassy Tokens
{% endhint %}

{% hint style="danger" %}
These tokens are secret and the compromise of such tokens would allow malicious actors to execute your workflows or upload packages to the Chassy Index on your behalf. It is strongly recommended to take care to keep them safe using best practices.
{% endhint %}

## How to generate Chassy Tokens

This guide assumes you already have a Workspace. If you do not, please consult our guide instructing how to [Create a Workspace](/getting-started/create-a-workspace.md).

First, navigate to the *Settings* tab in the Chassy Console. There, you will see your account settings.

<figure><img src="/files/R0VX7Y6flP2JHpR0jDRC" alt="The Generate Chassy Token section is below the Permissions section on the Settings tab."><figcaption></figcaption></figure>

To generate your token, just click the *Generate* button. Upon success, you'll see the censored token accompanied by a *Copy* button.

<figure><img src="/files/o84yWQD61Tn8dWNSnXmX" alt="Use the Copy button on the right of the censored token."><figcaption></figcaption></figure>

Clicking the *Copy* button will copy the token to your clipboard for use elsewhere.&#x20;

## Providing a token to your GitHub actions

To protect your secret, it is recommended that you use GitHub Secrets (see [documentation](https://docs.github.com/en/actions/security-for-github-actions/security-guides/using-secrets-in-github-actions)) to store and reference your secret in Actions workflows.

If you named your secret "CHASSY\_TOKEN", you can then define the `CHASSY_TOKEN` environment variable as follows:

```yaml
env:
    CHASSY_TOKEN: ${{ secrets.CHASSY_TOKEN }}
```


---

# 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.chassy.io/operator-guides/generate-chassy-tokens.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.