---
canonical: https://amplience.com/developers/docs/release-notes/2025/personal-access-token-approval/
title: Creating PATs in Dynamic Content
description: This release introduces a new feature to make it easy to create and manage Personal access tokens in Dynamic Content
audience: Business User
image: https://cdn.media.amplience.net/i/ampproduct/pat-approval-flow-2?w=1200&h=630
image_width: 1200
image_height: 630
date_published: 2025-03-24
date_modified: 2026-05-28
---

# Creating PATs in Dynamic Content

**Release date: 9th April 2025**

[Personal access tokens](https://amplience.com/developers/docs/apis/authorization/personal-access-tokens/) (PATs) are a self service alternative to using an API key and secret for authorizing access to the [Dynamic Content Management API](https://amplience.com/developers/docs/apis/content-management/) and [GraphQL Asset Management API](https://amplience.com/developers/docs/apis/asset-management/). You can now create and manage PATs using Dynamic Content, even if you are not an organization admin.

In this release we've also updated the [CLI Tool](https://amplience.com/developers/docs/dev-tools/cli-tool/setting-up-cli-tool/#setting-up-your-access) so that PATs can be used instead of an API Key and secret.

## Creating a PAT in Dynamic Content

To create a PAT in Dynamic Content, choose "Personal Access Tokens" from the Development menu, give the token a name, and click "Create token".

![Creating a new Personal Access Token](https://cdn.media.amplience.net/i/ampproduct/pat-approval-flow-2?w=1880&fmt=png 'Creating a new Personal Access Token')

There is a limit of 5 PATs per user per organization. If you are an organization admin and don't already have 5 tokens added in this account, then the token will be created immediately and be available for use in API requests. If you're not an organization admin, then the token creation request will be sent to your admin for approval.

Ensure that you copy the token because you won't be able to access it again. (Note that the token shown in the image below is not an active token).

![If the token is not created by an organization admin, then the request is sent for approval](https://cdn.media.amplience.net/i/ampproduct/pat-approval-flow-non-admin-2?w=1880&fmt=png 'If the token is not created by an organization admin, then the request is sent for approval')

### Approving a token creation request

If a user who is not an organization admin creates a token, the request is sent for approval. When the organization admin logs into [Account Management](https://amplience.com/developers/docs/user-guides/manage-accounts/overview/#accessing-account-management), the request is shown under the [approvals tab](https://amplience.com/developers/docs/user-guides/manage-accounts/overview/#approvals-tab).

![If the token is not created by an organization admin, then the request is sent for approval](https://cdn.media.amplience.net/i/ampproduct/pat-approval-flow-non-admin-5?w=1880&fmt=png 'If the token is not created by an organization admin, then the request is sent for approval')

Once approved, the token is shown in the list, together with any tokens you previously created, and is available to use with the [Dynamic Content Management API](https://amplience.com/developers/docs/apis/content-management/content-management-overview/), [GraphQL Asset Management API](https://amplience.com/developers/docs/apis/asset-management/overview/) or the [CLI tool](#using-pats-in-the-cli-tool).

![The token is shown in the list, but is only available once approved](https://cdn.media.amplience.net/i/ampproduct/pat-approval-flow-non-admin-6?w=1880&fmt=png 'The token is shown in the list, but is only available once approved')

## Using PATs in the CLI tool

You now have a choice of how to authenticate commands using the [CLI tool](https://amplience.com/developers/docs/dev-tools/cli-tool/), either using an API key and secret, or a PAT.

To use a PAT instead of an API key and secret, include the token in a command using the `--patToken` parameter, as shown in the content type schema export command below. The PAT shown in this example is truncated.

```
dc-cli content-type-schema export exportedSchemas  --hubId 6452aa021a7f3574f598716f  --patToken amp_pat_0VDv5arwRUK7PmNWYZIOrQ…
```

The PAT can either be included on the command line or read from the [configuration file](https://amplience.com/developers/docs/dev-tools/cli-tool/setting-up-cli-tool/#configuration). You can write the PAT to a configuration file as follows.

```
dc-cli configure --patToken amp_pat_0VDv5arwRUK7PmNWYZIOrQ… --hubId 6452aa021a7f3574f598716f
```

## Related pages

[Personal access tokens](https://amplience.com/developers/docs/apis/authorization/personal-access-tokens/)

[Content Management API](https://amplience.com/developers/docs/apis/content-management/content-management-overview/)

[GraphQL Asset Management API](https://amplience.com/developers/docs/apis/asset-management/overview/)

[CLI tool](https://amplience.com/developers/docs/dev-tools/cli-tool/)