Last pass for features, ready for final review

sarahsanders-docker · sarahsanders-docker · commit 40f53ebeaec2 · 2025-01-21T08:49:21.000-08:00
diff --git a/content/manuals/admin/deactivate-account.md b/content/manuals/admin/deactivate-account.md
@@ -6,6 +6,8 @@ aliases:
 - /docker-hub/deactivate-account/
 ---
 
+{{< summary-bar feature_name="General admin" >}}
+
 You can deactivate an account at any time. This section describes the prerequisites and steps to deactivate an organization account. For information on deactivating a user account, see [Deactivate a user account](../accounts/deactivate-user-account.md).
 
 > [!WARNING]
diff --git a/content/manuals/admin/organization/convert-account.md b/content/manuals/admin/organization/convert-account.md
@@ -7,6 +7,8 @@ aliases:
 - /docker-hub/convert-account/
 ---
 
+{{< summary-bar feature_name="Admin orgs" >}}
+
 You can convert an existing user account to an organization. This is useful if you need multiple users to access your account and the repositories that it’s connected to. Converting it to an organization gives you better control over permissions for these users through [teams](manage-a-team.md) and [roles](roles-and-permissions.md).
 
 When you convert a user account to an organization, the account is migrated to a Docker Team plan.
diff --git a/content/manuals/admin/organization/manage-a-team.md b/content/manuals/admin/organization/manage-a-team.md
@@ -8,6 +8,8 @@ aliases:
 - /docker-hub/manage-a-team/
 ---
 
+{{< summary-bar feature_name="Admin orgs" >}}
+
 You can create teams for your organization in Docker Hub and the Docker Admin Console. You can [configure repository access for a team](#configure-repository-permissions-for-a-team) in Docker Hub.
 
 A team is a group of Docker users that belong to an organization. An organization can have multiple teams. An organization owner can then create new teams and add members to an existing team using their Docker ID or email address and by selecting a team the user should be part of. Members aren't required to be part of a team to be associated with an organization.
diff --git a/content/manuals/admin/organization/manage-products.md b/content/manuals/admin/organization/manage-products.md
@@ -5,6 +5,8 @@ description: Learn how to manage Docker products for your organization
 keywords: organization, tools, products
 ---
 
+{{< summary-bar feature_name="Admin orgs" >}}
+
 In this section, learn how to manage access and view usage of the Docker
 products for your organization. For more detailed information about each
 product, including how to set up and configure them, see the following manuals:
diff --git a/content/manuals/admin/organization/members.md b/content/manuals/admin/organization/members.md
@@ -197,6 +197,8 @@ To update a member role:
 
 ## Export members CSV file
 
+{{< summary-bar feature_name="Admin orgs" >}}
+
 Owners can export a CSV file containing all members. The CSV file for a company contains the following fields:
 - Name: The user's name
 - Username: The user's Docker ID
diff --git a/content/manuals/admin/organization/onboard.md b/content/manuals/admin/organization/onboard.md
@@ -11,6 +11,8 @@ aliases:
 - /docker-hub/onboard-business/
 ---
 
+{{< summary-bar feature_name="Admin orgs" >}}
+
 {{< include "admin-early-access.md" >}}
 
 Learn how to onboard your organization using Docker Hub or the Docker Admin Console.
diff --git a/content/manuals/admin/organization/orgs.md b/content/manuals/admin/organization/orgs.md
@@ -8,6 +8,8 @@ aliases:
 - /docker-hub/orgs/
 ---
 
+{{< summary-bar feature_name="Admin orgs" >}}
+
 This section describes how to create an organization. Before you begin:
 
 - You need a [Docker ID](/accounts/create-account/)
diff --git a/content/manuals/build-cloud/_index.md b/content/manuals/build-cloud/_index.md
@@ -11,6 +11,8 @@ aliases:
   - /build/cloud/
 ---
 
+{{< summary-bar feature_name="Docker Build Cloud" >}}
+
 Docker Build Cloud is a service that lets you build your container images
 faster, both locally and in CI. Builds run on cloud infrastructure optimally
 dimensioned for your workloads, no configuration required. The service uses a
diff --git a/content/manuals/desktop/features/synchronized-file-sharing.md b/content/manuals/desktop/features/synchronized-file-sharing.md
@@ -7,9 +7,7 @@ aliases:
 - /desktop/synchronized-file-sharing/
 ---
 
-> [!NOTE]
->
-> Synchronized file shares is available with Docker Desktop version 4.27 and later. It is available for customers with a Docker Pro, Team, or Business subscription. 
+{{< summary-bar feature_name="Synchronized file sharing" >}}
 
 Synchronized file shares is an alternative file sharing mechanism that provides fast and flexible host-to-VM file sharing, enhancing bind mount performance through the use of synchronized filesystem caches. 
 
diff --git a/content/manuals/security/for-admins/enforce-sign-in/_index.md b/content/manuals/security/for-admins/enforce-sign-in/_index.md
@@ -11,6 +11,8 @@ aliases:
 weight: 30
 ---
 
+{{< summary-bar feature_name="Enforce sign-in" >}}
+
 By default, members of your organization can use Docker Desktop without signing
 in. When users don’t sign in as a member of your organization, they don’t
 receive the [benefits of your organization’s
diff --git a/content/manuals/security/for-admins/enforce-sign-in/methods.md b/content/manuals/security/for-admins/enforce-sign-in/methods.md
@@ -6,6 +6,8 @@ tags: [admin]
 linkTitle: Methods
 ---
 
+{{< summary-bar feature_name="Enforce sign-in" >}}
+
 This page outlines the different methods for enforcing sign-in for Docker Desktop.
 
 ## Registry key method (Windows only)
diff --git a/content/manuals/security/for-admins/hardened-desktop/_index.md b/content/manuals/security/for-admins/hardened-desktop/_index.md
@@ -32,9 +32,7 @@ grid:
 weight: 60
 ---
 
-> [!NOTE]
->
-> Hardened Docker Desktop is available to Docker Business customers only.
+{{< summary-bar feature_name="Hardened Docker Desktop" >}}
 
 Hardened Docker Desktop is a group of security features, designed to improve the security of developer environments with minimal impact on developer experience or productivity.
 
diff --git a/content/manuals/security/for-admins/hardened-desktop/air-gapped-containers.md b/content/manuals/security/for-admins/hardened-desktop/air-gapped-containers.md
@@ -7,7 +7,7 @@ aliases:
  - /desktop/hardened-desktop/air-gapped-containers/
 ---
 
-{{< introduced desktop 4.29.0 "/manuals/desktop/release-notes.md#4290" >}}
+{{< summary-bar feature_name="Air-gapped containers" >}}
 
 Air-gapped containers let you restrict containers from accessing network resources, limiting where data can be uploaded to or downloaded from.
 
diff --git a/content/manuals/security/for-admins/hardened-desktop/enhanced-container-isolation/_index.md b/content/manuals/security/for-admins/hardened-desktop/enhanced-container-isolation/_index.md
@@ -9,13 +9,11 @@ aliases:
 weight: 20
 ---
 
-> [!NOTE]
->
-> Enhanced Container Isolation is available to Docker Business customers only.
+{{< summary-bar feature_name="Hardened Docker Desktop" >}}
 
 Enhanced Container Isolation (ECI) provides an additional layer of security to prevent malicious workloads running in containers from compromising Docker Desktop or the host.
 
-It uses a variety of advanced techniques to harden container isolation, but without impacting developer productivity. 
+It uses a variety of advanced techniques to harden container isolation, but without impacting developer productivity.
 
 Enhanced Container Isolation ensures stronger container isolation and also locks in any security configurations that have been created by administrators, for instance through [Registry Access Management policies](/manuals/security/for-admins/hardened-desktop/registry-access-management.md) or with [Settings Management](../settings-management/_index.md).
 
diff --git a/content/manuals/security/for-admins/hardened-desktop/enhanced-container-isolation/config.md b/content/manuals/security/for-admins/hardened-desktop/enhanced-container-isolation/config.md
@@ -8,6 +8,8 @@ aliases:
 weight: 30
 ---
 
+{{< summary-bar feature_name="Hardened Docker Desktop" >}}
+
 ## Docker socket mount permissions
 
 By default, when Enhanced Container Isolation (ECI) is enabled, Docker Desktop does not allow bind-mounting the
diff --git a/content/manuals/security/for-admins/hardened-desktop/enhanced-container-isolation/features-benefits.md b/content/manuals/security/for-admins/hardened-desktop/enhanced-container-isolation/features-benefits.md
@@ -2,11 +2,13 @@
 description: The benefits of enhanced container isolation
 title: Key features and benefits
 keywords: set up, enhanced container isolation, rootless, security, features, Docker Desktop
-aliases: 
+aliases:
  - /desktop/hardened-desktop/enhanced-container-isolation/features-benefits/
 weight: 20
 ---
 
+{{< summary-bar feature_name="Hardened Docker Desktop" >}}
+
 ## Linux user namespace on all containers
 
 With Enhanced Container Isolation, all user containers leverage the [Linux user namespace](https://man7.org/linux/man-pages/man7/user_namespaces.7.html)
diff --git a/content/manuals/security/for-admins/hardened-desktop/enhanced-container-isolation/how-eci-works.md b/content/manuals/security/for-admins/hardened-desktop/enhanced-container-isolation/how-eci-works.md
@@ -2,11 +2,13 @@
 description: How Enhanced Container Isolation works
 title: How does it work?
 keywords: set up, enhanced container isolation, rootless, security
-aliases: 
+aliases:
  - /desktop/hardened-desktop/enhanced-container-isolation/how-eci-works/
 weight: 10
 ---
 
+{{< summary-bar feature_name="Hardened Docker Desktop" >}}
+
 Docker implements Enhanced Container Isolation by using the [Sysbox
 container runtime](https://github.com/nestybox/sysbox). Sysbox is a fork of the
 standard OCI runc runtime that was modified to enhance standard container isolation and
diff --git a/content/manuals/security/for-admins/hardened-desktop/image-access-management.md b/content/manuals/security/for-admins/hardened-desktop/image-access-management.md
@@ -11,9 +11,7 @@ aliases:
 weight: 40
 ---
 
-> [!NOTE]
->
-> Image Access Management is available to [Docker Business](/manuals/subscription/details.md#docker-business) customers only.
+{{< summary-bar feature_name="Hardened Docker Desktop" >}}
 
 Image Access Management gives you control over which types of images, such as Docker Official Images, Docker Verified Publisher Images, or community images, your developers can pull from Docker Hub.
 
diff --git a/content/manuals/security/for-admins/hardened-desktop/settings-management/_index.md b/content/manuals/security/for-admins/hardened-desktop/settings-management/_index.md
@@ -10,9 +10,7 @@ aliases:
 weight: 10
 ---
 
-> [!NOTE]
->
-> Settings Management is available to Docker Business customers only.
+{{< summary-bar feature_name="Hardened Docker Desktop" >}}
 
 Settings Management helps you control key Docker Desktop settings, like proxies and network configurations, on your developers' machines within your organization.
 
diff --git a/content/manuals/security/for-admins/hardened-desktop/settings-management/configure-json-file.md b/content/manuals/security/for-admins/hardened-desktop/settings-management/configure-json-file.md
@@ -9,9 +9,7 @@ aliases:
  - /security/for-admins/hardened-desktop/settings-management/configure/
 ---
 
-> [!NOTE]
->
-> Settings Management is available to Docker Business customers only.
+{{< summary-bar feature_name="Hardened Docker Desktop" >}}
 
 This page contains information on how to configure Settings Management with an `admin-settings.json` file. You can specify and lock configuration parameters to create a standardized Docker Desktop environment across your company or organization.
 
diff --git a/content/manuals/security/for-admins/provisioning/_index.md b/content/manuals/security/for-admins/provisioning/_index.md
@@ -6,6 +6,8 @@ linkTitle: Provision
 weight: 20
 ---
 
+{{< summary-bar feature_name="SSO" >}}
+
 Once you've configured your SSO connection, the next step is to provision users. This process ensures that users can access your organization.
 This guide provides an overview of user provisioning and supported provisioning methods.
 
diff --git a/content/manuals/security/for-admins/provisioning/group-mapping.md b/content/manuals/security/for-admins/provisioning/group-mapping.md
@@ -10,6 +10,8 @@ aliases:
 weight: 40
 ---
 
+{{< summary-bar feature_name="SSO" >}}
+
 Group mapping lets you sync user groups from your identity provider (IdP) with teams in your Docker organization. This automates team membership management, keeping your Docker teams up to date based on changes in your IdP. You can use group mapping once you have configured [single sign-on (SSO)](../single-sign-on/_index.md).
 
 > [!TIP]
diff --git a/content/manuals/security/for-admins/provisioning/just-in-time.md b/content/manuals/security/for-admins/provisioning/just-in-time.md
@@ -5,6 +5,8 @@ title: Just-in-Time provisioning
 linkTitle: Just-in-Time
 ---
 
+{{< summary-bar feature_name="SSO" >}}
+
 Just-in-Time (JIT) provisioning automatically creates and updates user accounts after every successful single sign-on (SSO) authentication. JIT verifies that the user signing in belongs to the organization and the teams assigned to them in your identity provider (IdP). When you [create your SSO connection](../single-sign-on/_index.md), JIT provisioning is turned on by default.
 
 ## SSO authentication with JIT provisioning enabled
diff --git a/content/manuals/security/for-admins/provisioning/scim.md b/content/manuals/security/for-admins/provisioning/scim.md
@@ -9,6 +9,8 @@ aliases:
 weight: 30
 ---
 
+{{< summary-bar feature_name="SSO" >}}
+
 System for Cross-domain Identity Management (SCIM) is available for Docker Business customers. This guide provides an overview of SCIM provisioning.
 
 ## How SCIM works
diff --git a/content/manuals/security/for-admins/roles-and-permissions.md b/content/manuals/security/for-admins/roles-and-permissions.md
@@ -2,13 +2,15 @@
 description: >
   Use roles in your organization to control who has access to content,
   registry, and organization management permissions.
-keywords: members, teams, organization, company, roles, access, docker hub, admin console, security 
+keywords: members, teams, organization, company, roles, access, docker hub, admin console, security
 title: Roles and permissions
 aliases:
 - /docker-hub/roles-and-permissions/
 weight: 40
 ---
 
+{{< summary-bar feature_name="General admin" >}}
+
 Organization and company owners can assign roles to individuals giving them different permissions in the organization. This guide outlines Docker's organization roles and their permission scopes.
 
 ## Roles
diff --git a/content/manuals/security/for-admins/single-sign-on/_index.md b/content/manuals/security/for-admins/single-sign-on/_index.md
@@ -10,6 +10,8 @@ aliases:
 weight: 10
 ---
 
+{{< summary-bar feature_name="SSO" >}}
+
 Single sign-on (SSO) lets users access Docker by authenticating using their identity providers (IdPs). SSO is available for a whole company, and all associated organizations within that company, or an individual organization that has a Docker Business subscription. To upgrade your existing account to a Docker Business subscription, see [Upgrade your subscription](/subscription/upgrade/).
 
 ## How SSO works
diff --git a/content/manuals/security/for-admins/single-sign-on/configure.md b/content/manuals/security/for-admins/single-sign-on/configure.md
@@ -1,6 +1,6 @@
 ---
 description: Learn how to configure single sign-on for your organization or company.
-keywords: configure, sso, docker hub, hub, docker admin, admin, security 
+keywords: configure, sso, docker hub, hub, docker admin, admin, security
 title: Configure single sign-on
 linkTitle: Configure
 aliases:
@@ -12,6 +12,8 @@ aliases:
 - /admin/organization/security-settings/sso-configuration/
 ---
 
+{{< summary-bar feature_name="SSO" >}}
+
 Get started creating a single sign-on (SSO) connection for your organization or company. This guide walks through the steps to add and verify the domains your members use to sign in to Docker.
 
 ## Step one: Add your domain
diff --git a/content/manuals/security/for-admins/single-sign-on/connect.md b/content/manuals/security/for-admins/single-sign-on/connect.md
@@ -5,6 +5,8 @@ title: Create an SSO connection
 linkTitle: Connect
 ---
 
+{{< summary-bar feature_name="SSO" >}}
+
 Creating a single sign-on (SSO) connection requires setting up the connection in Docker first, followed by setting up the connection in your identity provider (IdP). This guide provides steps for setting up your SSO connection in Docker and your IdP.
 
 > [!TIP]
diff --git a/content/manuals/security/for-admins/single-sign-on/manage.md b/content/manuals/security/for-admins/single-sign-on/manage.md
@@ -8,6 +8,8 @@ aliases:
 - /single-sign-on/manage/
 ---
 
+{{< summary-bar feature_name="SSO" >}}
+
 ## Manage organizations
 
 > [!NOTE]
diff --git a/data/summary.yaml b/data/summary.yaml
@@ -5,6 +5,11 @@ Admin Console:
   subscription: [Business]
   availability: Early access
   for: Administrators
+Admin orgs:
+  subscription: [Team, Business]
+  for: Administrators
+Air-gapped containers:
+  requires: Docker Desktop 4.29.0 and later
 Allow list:
   for: Administrators
 Amazon S3 cache:
@@ -31,6 +36,8 @@ containerd:
   availability: Experimental
 Dev Environments:
   availability: Beta
+Docker Build Cloud:
+  subscription: [Pro, Team, Business]
 docker compose alpha:
   availability: Experimental
 Docker Desktop Archlinux:
@@ -51,10 +58,16 @@ Docker Scout health scores:
 Domain audit:
   subscription: [Business]
   for: Administrators
+Enforce sign-in:
+  subscription: [Business]
+  for: Administrators
 General admin:
   for: Administrators
 GitHub Actions cache:
   availability: Experimental
+Hardened Docker Desktop:
+  subscription: [Business]
+  for: Administrators
 Import builds:
   availability: Beta
   requires: Docker Desktop 4.31 and later
@@ -87,6 +100,9 @@ Registry access management:
 SSO:
   subscription: [Business]
   for: Administrators
+Synchronized file sharing:
+  subscription: [Pro, Team, Business]
+  requires: Docker Desktop 4.27 and later
 USB/IP support:
   requires: Docker Desktop 4.35.0 and later
 VMM:
