> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/~/revisions/1AlFSZBNMIBgs7fiOwFD/managed-services/container-registry/dcd-how-tos/create-a-token.md).

# Create a Token

Once you have created a Container Registry, you will want to create one or more tokens to provide (and control) access to your registry.

### Create a Token

1\. To create a Token for a Container Registry, go to **Menu** > **Containers** > **Container Registry**.

![Access the Container Registry Manager](/files/i6RSEJmWxCxUlGT9f5XZ)

2\. In the **Container Registry Manager**, select the Container Registry that you want to configure.

![Select a Running Container Registry](/files/EsSogN9BuGNlTE0WGAvr)

3\. Click on the **+ Add** in the **Tokens** section to create a new Token

![Add a Token in the detail view for the relevant Container Registry](/files/P53n0MAwY1fj6bhOPxkY)

4\. Complete the following fields:

* **Name**\
  This is a user-visible name for the token so that it can be easily identified
* **Status**\
  Leave as **Enabled**. The token can be **Disabled** at a later date if required
* **Expiry Date** (if required)
* **Scopes**:\
  Scopes define what actions the token has permission to perform and on which repositories. You must have at least one scope added (by clicking the **Add scope** button). You can have multiple scopes if the token needs different permissions per repository.
  * **Name**\
    List the names of the repositories to which the token will have access. `*` can be used as a wildcard. `*` will provide access to all repositories
  * **Actions**\
    Select the required **Actions** for the token (**Pull**, **Push** and/or **Delete**)
  * **Type**\
    Choose either **repository** or **registry**. Use **registry** to get the list of repositories in the registry. Use **repository** to manage the contents of the repository(s)
  * Click **Add scope** and add further scopes if needed

5\. Click **Save**

![Provide the necessary information and create the token](/files/sP5wdsGIwfAqwGDC9BRR)

6\. You are then presented with the details of the created credential and the Docker Login command using the newly created token.

![Your are presented with important toekn credentials](/files/F0PREkHb2dtbceR3rAGa)

{% hint style="info" %}
**Note:** This is the only time you will be able to access the password for this token. It is not possible to recover the password for a token so you must store it securely and safely.
{% endhint %}


---

# 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.ionos.com/cloud/~/revisions/1AlFSZBNMIBgs7fiOwFD/managed-services/container-registry/dcd-how-tos/create-a-token.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.