diff --git a/content/manuals/security/authentication/oidc-connections/_index.md b/content/manuals/security/authentication/oidc-connections/_index.md
index fe3b79d2d12a..bbde0f6f64b7 100644
--- a/content/manuals/security/authentication/oidc-connections/_index.md
+++ b/content/manuals/security/authentication/oidc-connections/_index.md
@@ -2,7 +2,7 @@
 title: OIDC connections overview
 linkTitle: OIDC connections
 description: Authenticate GitHub Actions to Docker with short-lived OpenID Connect tokens
-keywords: oidc connections, openid connect, github actions, jwt, subject claims, rulesets, enterprise security, workload authentication
+keywords: oidc connections, openid connect, github actions, jwt, subject claims, rulesets, connection limits, enterprise security, workload authentication
 tags: [admin]
 weight: 35
 aliases:
@@ -20,8 +20,9 @@ vendor that can grant fine-grained access to your Docker resources.
 
 OIDC connections follow the OpenID Connect (OIDC) standard. Establishing a
 trust relationship involves creating the connection, configuring a
-workflow, and testing. A connection, then, is the named trust relationship in Docker Home that workflows point to. For example, a trust relationship between Docker and
-GitHub follows these steps:
+workflow, and testing. A connection, then, is the named trust relationship
+in Docker Home that workflows point to. For example, a trust relationship
+between Docker and GitHub follows these steps:
 
 - GitHub issues a JWT ID token for the workflow run.
 - During authentication, Docker:
@@ -37,6 +38,25 @@ and issued on a per-workflow basis.
 For how OIDC connections compare to organization access tokens, see
 [Access tokens](/manuals/security/access-tokens/_index.md).
 
+## Connection limits
+
+The number of OIDC connections an organization can have depends on its
+subscription:
+
+| Subscription | Maximum OIDC connections |
+| :----------- | :----------------------- |
+| Team         | 10                       |
+| [Docker-Sponsored Open Source](/manuals/docker-hub/repos/manage/trusted-content/dsos-program.md) | 10 |
+| Business     | 100                      |
+
+Active and deactivated connections count toward the limit, but deleted
+connections don't. When your organization reaches the limit, the
+**Create OIDC connection** button is disabled. To create another
+connection, delete one you no longer need.
+
+Each connection can have up to five rulesets. See
+[Rulesets](/manuals/security/authentication/oidc-connections/rulesets-claims.md#rulesets).
+
 ## Next steps
 
 - [Create an OIDC connection](/manuals/security/authentication/oidc-connections/create-manage.md)
diff --git a/content/manuals/security/authentication/oidc-connections/rulesets-claims.md b/content/manuals/security/authentication/oidc-connections/rulesets-claims.md
index d9bf92b30b47..08fb7e47b953 100644
--- a/content/manuals/security/authentication/oidc-connections/rulesets-claims.md
+++ b/content/manuals/security/authentication/oidc-connections/rulesets-claims.md
@@ -35,7 +35,9 @@ Each ruleset has these fields:
 
 You can add one to five rulesets on a connection. If more than one
 ruleset matches a token, Docker grants the union of their resources and
-scopes.
+scopes. Your subscription also limits how many connections your
+organization can have. See
+[Connection limits](/manuals/security/authentication/oidc-connections/_index.md#connection-limits).
 
 ## Subject claims