Skip to content

Commit 3c4b9ac

Browse files
add beta label
Signed-off-by: Craig <[email protected]>
1 parent c2d2564 commit 3c4b9ac

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

content/manuals/security/for-admins/access-tokens.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,18 +3,19 @@ title: Organization access tokens
33
description: Learn how to create and manage organization access tokens
44
to securely push and pull images programmatically.
55
keywords: docker hub, security, OAT, organization access token
6+
linkTitle: Organization access tokens (Beta)
67
---
78

8-
> [!NOTE]
9-
>
10-
> Organization access tokens require a
11-
> [Docker Team, or Business subscription](/subscription/core-subscription/details/).
9+
{{% experimental title="Beta" %}}
10+
The organization access tokens feature is currently in [Beta](../../release-lifecycle.md#beta).
11+
{{% /experimental %}}
1212

1313
An organization access token (OAT) is like a [personal access token
1414
(PAT)](/security/for-developers/access-tokens/), but an OAT is associated with
1515
an organization and not a single user account. Use an OAT instead of a PAT to
1616
let business-critical tasks access Docker Hub repositories without connecting
17-
the token to single user.
17+
the token to single user. You must have a [Docker Team or Business
18+
subscription](/subscription/core-subscription/details/) to use OATs.
1819

1920
OATs provide the following advantages:
2021

0 commit comments

Comments
 (0)