> For the complete documentation index, see [llms.txt](https://know.rendernetwork.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://know.rendernetwork.com/docs/web-app/access-keys.md).

# Access tokens

Create and manage access tokens for signing in, connecting tools, and using the API.

An access token lets a tool work with your Render Network account using the permissions you choose. It can also be used to [sign in to the web app](/docs/get-started/sign-in.md).

## Tokens created in the old web app

{% hint style="warning" %}
If you use a token created in the old web app, we recommend [creating a replacement](#create-and-copy-a-token) in the redesigned web app. The redesigned app needs additional permissions that an older token may not include.

Choose the [permissions you need](#choose-permissions), then switch the app or connected tool to the replacement. Check that it works before revoking the old token.
{% endhint %}

## Create and copy a token

1. Click your name or account icon at the bottom of the sidebar, then open **Access Tokens**.
2. Click **Create New Token**.
3. Enter a recognisable **Token name**, such as the name of the tool you will connect.
4. Select at least one permission and click **Create**.
5. In the token's row, click the copy action, labelled **Copy access token** when you hover over it. Paste the token into the tool that requested it.

Tokens remain available to copy from this list; you do not have to save the value during creation.

{% hint style="warning" %}
Anyone with the token can use its permissions on your account. Keep it private. If it has been shared by mistake, revoke it and create a replacement.
{% endhint %}

## Choose permissions

Permissions are shown as **Scopes** in the token list. They control what the token can access, such as **Scenes**, **Jobs**, **Frames**, or **Frame Outputs**. Follow the connected tool's instructions for the permissions it needs.

For your own full access to the web app, select **All permissions**. Use that option only for personal use.

If you signed in with a token, you can only grant permissions that token already has. Sign in with your OTOY account to manage the full set. This also makes **Access Tokens** available if it is missing from your account menu.

## Change a name or permissions

In an active token's row, click the edit action. Update **Token name** or the selected permissions in **Edit Token Name & Permissions**, then click **Save**.

**Last Used** displays **Not available**, so it cannot tell you whether a tool still uses that token.

## Revoke or delete a token

| Action in the token's row | What happens after confirmation                                           |
| ------------------------- | ------------------------------------------------------------------------- |
| **Revoke access token**   | The token stops granting access and remains in the list as **Revoked**.   |
| **Delete access token**   | The token stops granting access and is permanently removed from the list. |

Connected tools using that token lose access. Reconfigure them with another token if they still need to connect.

If a message says a token change could not be verified, refresh the page and check its state before trying again.


---

# 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://know.rendernetwork.com/docs/web-app/access-keys.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.