docker · aevesdocker · Jul 18, 2025 · Jul 16, 2025 · Jul 16, 2025
diff --git a/content/guides/admin-set-up/testing.md b/content/guides/admin-set-up/testing.md
@@ -10,7 +10,7 @@
 
 > [!IMPORTANT] 
 >
-> Some users may need CLI based logins to Docker Hub, and for this they will need a [personal access token (PAT)](/manuals/security/for-developers/access-tokens.md).
+> Some users may need CLI based logins to Docker Hub, and for this they will need a [personal access token (PAT)](/manuals/security/access-tokens.md).
 
 ## Test RAM and IAM
 

diff --git a/content/guides/bun/configure-ci-cd.md b/content/guides/bun/configure-ci-cd.md
@@ -31,7 +31,7 @@ Create a GitHub repository, configure the Docker Hub credentials, and push your
 
 3. Create a new **Repository variable** named `DOCKER_USERNAME` and your Docker ID as a value.
 
-4. Create a new [Personal Access Token (PAT)](/manuals/security/for-developers/access-tokens.md#create-an-access-token)for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
+4. Create a new [Personal Access Token (PAT)](/manuals/security/access-tokens.md#create-an-access-token)for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
 
 5. Add the PAT as a **Repository secret** in your GitHub repository, with the name
    `DOCKERHUB_TOKEN`.

diff --git a/content/guides/cpp/configure-ci-cd.md b/content/guides/cpp/configure-ci-cd.md
@@ -32,7 +32,7 @@ Create a GitHub repository, configure the Docker Hub credentials, and push your
 
 3. Create a new **Repository variable** named `DOCKER_USERNAME` and your Docker ID as a value.
 
-4. Create a new [Personal Access Token (PAT)](/manuals/security/for-developers/access-tokens.md#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
+4. Create a new [Personal Access Token (PAT)](/manuals/security/access-tokens.md#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
 
 5. Add the PAT as a **Repository secret** in your GitHub repository, with the name
    `DOCKERHUB_TOKEN`.

diff --git a/content/guides/deno/configure-ci-cd.md b/content/guides/deno/configure-ci-cd.md
@@ -31,7 +31,7 @@ Create a GitHub repository, configure the Docker Hub credentials, and push your
 
 3. Create a new **Repository variable** named `DOCKER_USERNAME` and your Docker ID as a value.
 
-4. Create a new [Personal Access Token (PAT)](/manuals/security/for-developers/access-tokens.md#create-an-access-token)for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
+4. Create a new [Personal Access Token (PAT)](/manuals/security/access-tokens.md#create-an-access-token)for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
 
 5. Add the PAT as a **Repository secret** in your GitHub repository, with the name
    `DOCKERHUB_TOKEN`.

diff --git a/content/guides/dotnet/configure-ci-cd.md b/content/guides/dotnet/configure-ci-cd.md
@@ -32,7 +32,7 @@ Create a GitHub repository, configure the Docker Hub credentials, and push your
 
 3. Create a new **Repository variable** named `DOCKER_USERNAME` and your Docker ID as a value.
 
-4. Create a new [Personal Access Token (PAT)](/manuals/security/for-developers/access-tokens.md#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
+4. Create a new [Personal Access Token (PAT)](/manuals/security/access-tokens.md#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
 
 5. Add the PAT as a **Repository secret** in your GitHub repository, with the name
    `DOCKERHUB_TOKEN`.

diff --git a/content/guides/gha.md b/content/guides/gha.md
@@ -51,7 +51,7 @@ that, you must authenticate with your Docker credentials (username and access
 token) as part of the GitHub Actions workflow.
 
 For instructions on how to create a Docker access token, see
-[Create and manage access tokens](/manuals/security/for-developers/access-tokens.md).
+[Create and manage access tokens](/manuals/security/access-tokens.md).
 
 Once you have your Docker credentials ready, add the credentials to your GitHub
 repository so you can use them in GitHub Actions:

diff --git a/content/guides/golang/configure-ci-cd.md b/content/guides/golang/configure-ci-cd.md
@@ -32,7 +32,7 @@ Create a GitHub repository, configure the Docker Hub credentials, and push your
 
 3. Create a new **Repository variable** named `DOCKER_USERNAME` and your Docker ID as a value.
 
-4. Create a new [Personal Access Token (PAT)](/manuals/security/for-developers/access-tokens.md#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
+4. Create a new [Personal Access Token (PAT)](/manuals/security/access-tokens.md#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
 
 5. Add the PAT as a **Repository secret** in your GitHub repository, with the name
    `DOCKERHUB_TOKEN`.

diff --git a/content/guides/java/configure-ci-cd.md b/content/guides/java/configure-ci-cd.md
@@ -32,7 +32,7 @@ Create a GitHub repository, configure the Docker Hub credentials, and push your
 
 3. Create a new **Repository variable** named `DOCKER_USERNAME` and your Docker ID as a value.
 
-4. Create a new [Personal Access Token (PAT)](/manuals/security/for-developers/access-tokens.md#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
+4. Create a new [Personal Access Token (PAT)](/manuals/security/access-tokens.md#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
 
 5. Add the PAT as a **Repository secret** in your GitHub repository, with the name
    `DOCKERHUB_TOKEN`.

diff --git a/content/guides/nodejs/configure-ci-cd.md b/content/guides/nodejs/configure-ci-cd.md
@@ -32,7 +32,7 @@ Create a GitHub repository, configure the Docker Hub credentials, and push your
 
 3. Create a new **Repository variable** named `DOCKER_USERNAME` and your Docker ID as a value.
 
-4. Create a new [Personal Access Token (PAT)](/manuals/security/for-developers/access-tokens.md#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
+4. Create a new [Personal Access Token (PAT)](/manuals/security/access-tokens.md#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
 
 5. Add the PAT as a **Repository secret** in your GitHub repository, with the name
    `DOCKERHUB_TOKEN`.

diff --git a/content/guides/php/configure-ci-cd.md b/content/guides/php/configure-ci-cd.md
@@ -32,7 +32,7 @@ Create a GitHub repository, configure the Docker Hub credentials, and push your
 
 3. Create a new **Repository variable** named `DOCKER_USERNAME` and your Docker ID as a value.
 
-4. Create a new [Personal Access Token (PAT)](/manuals/security/for-developers/access-tokens.md#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
+4. Create a new [Personal Access Token (PAT)](/manuals/security/access-tokens.md#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
 
 5. Add the PAT as a **Repository secret** in your GitHub repository, with the name
    `DOCKERHUB_TOKEN`.

diff --git a/content/guides/python/configure-github-actions.md b/content/guides/python/configure-github-actions.md
@@ -20,7 +20,7 @@ If you didn't create a [GitHub repository](https://github.com/new) for your proj
 
 2. Under the **Variables** tab, create a new **Repository variable** named `DOCKER_USERNAME` and your Docker ID as a value.
 
-3. Create a new [Personal Access Token (PAT)](/manuals/security/for-developers/access-tokens.md#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
+3. Create a new [Personal Access Token (PAT)](/manuals/security/access-tokens.md#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
 
 4. Add the PAT as a **Repository secret** in your GitHub repository, with the name
    `DOCKERHUB_TOKEN`.

diff --git a/content/guides/r/configure-ci-cd.md b/content/guides/r/configure-ci-cd.md
@@ -32,7 +32,7 @@ Create a GitHub repository, configure the Docker Hub credentials, and push your
 
 3. Create a new **Repository variable** named `DOCKER_USERNAME` and your Docker ID as a value.
 
-4. Create a new [Personal Access Token (PAT)](/manuals/security/for-developers/access-tokens.md#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
+4. Create a new [Personal Access Token (PAT)](/manuals/security/access-tokens.md#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
 
 5. Add the PAT as a **Repository secret** in your GitHub repository, with the name
    `DOCKERHUB_TOKEN`.

diff --git a/content/guides/ruby/configure-github-actions.md b/content/guides/ruby/configure-github-actions.md
@@ -20,7 +20,7 @@ If you didn't create a [GitHub repository](https://github.com/new) for your proj
 
 2. Under the **Variables** tab, create a new **Repository variable** named `DOCKER_USERNAME` and your Docker ID as a value.
 
-3. Create a new [Personal Access Token (PAT)](/manuals/security/for-developers/access-tokens.md#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
+3. Create a new [Personal Access Token (PAT)](/manuals/security/access-tokens.md#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
 
 4. Add the PAT as a **Repository secret** in your GitHub repository, with the name
    `DOCKERHUB_TOKEN`.

diff --git a/content/guides/rust/configure-ci-cd.md b/content/guides/rust/configure-ci-cd.md
@@ -32,7 +32,7 @@ Create a GitHub repository, configure the Docker Hub credentials, and push your
 
 3. Create a new **Repository variable** named `DOCKER_USERNAME` and your Docker ID as a value.
 
-4. Create a new [Personal Access Token (PAT)](/manuals/security/for-developers/access-tokens.md#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
+4. Create a new [Personal Access Token (PAT)](/manuals/security/access-tokens.md#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
 
 5. Add the PAT as a **Repository secret** in your GitHub repository, with the name
    `DOCKERHUB_TOKEN`.

diff --git a/content/manuals/accounts/_index.md b/content/manuals/accounts/_index.md
@@ -22,10 +22,10 @@ grid:
 - title: Personal access tokens
   description: Learn how to create and manage access tokens for your account.
   icon: password
-  link: /security/for-developers/access-tokens/
+  link: /security/access-tokens/
 - title: Set up two-factor authentication
   description: Add an extra layer of authentication to your Docker account.
-  link: /security/for-developers/2fa/
+  link: /security/2fa/
   icon: phonelink_lock
 - title: Deactivate an account
   description: Learn how to deactivate a Docker user account.

diff --git a/content/manuals/accounts/create-account.md b/content/manuals/accounts/create-account.md
@@ -77,7 +77,7 @@
 > When you use the `docker login` command, your credentials are
 stored in your home directory in `.docker/config.json`. The password is base64-encoded in this file.
 >
-> We recommend using one of the [Docker credential helpers](https://github.com/docker/docker-credential-helpers) for secure storage of passwords. For extra security, you can also use a [personal access token](../security/for-developers/access-tokens.md) to sign in instead, which is still encoded in this file (without a Docker credential helper) but doesn't permit administrator actions (such as changing the password).
+> We recommend using one of the [Docker credential helpers](https://github.com/docker/docker-credential-helpers) for secure storage of passwords. For extra security, you can also use a [personal access token](../security/access-tokens.md) to sign in instead, which is still encoded in this file (without a Docker credential helper) but doesn't permit administrator actions (such as changing the password).
 
 ### Sign in with your social provider
 

diff --git a/content/manuals/accounts/manage-account.md b/content/manuals/accounts/manage-account.md
@@ -60,12 +60,12 @@ Follow the instructions in the password reset email.
 
 To update your two-factor authentication (2FA) settings, select **2FA**.
 For information on two-factor authentication (2FA) for your account, see
-[Enable two-factor authentication](../security/for-developers/2fa/_index.md)
+[Enable two-factor authentication](../security/2fa/_index.md)
 to get started.
 
 To manage personal access tokens, select **Personal access tokens**.
 For information on personal access tokens, see
-[Create and manage access tokens](../security/for-developers/access-tokens.md).
+[Create and manage access tokens](../security/access-tokens.md).
 
 ## Manage connected accounts
 

@@ -37,7 +37,7 @@
 To enable your CI/CD system to build and push images using Docker Build Cloud, provide both an access token and a username. The type of token and the username you use depend on your account type and permissions.
 
 - If you are an organization administrator or have permission to create [organization access tokens (OAT)](/manuals/enterprise/security/access-tokens.md), use an OAT and set `DOCKER_ACCOUNT` to your Docker Hub organization name.
-- If you do not have permission to create OATs or are using a personal account, use a [personal access token (PAT)](/security/for-developers/access-tokens/) and set `DOCKER_ACCOUNT` to your Docker Hub username.
+- If you do not have permission to create OATs or are using a personal account, use a [personal access token (PAT)](/security/access-tokens/) and set `DOCKER_ACCOUNT` to your Docker Hub username.
 
 ### Creating access tokens
 
@@ -59,7 +59,7 @@
 
 #### For personal accounts
 
-- Create a [personal access token (PAT)](/security/for-developers/access-tokens/) with the following permissions:
+- Create a [personal access token (PAT)](/security/access-tokens/) with the following permissions:
    1. **Read & write** access.
         - Note: Building with Docker Build Cloud only requires read access, but you need write access to push images to a Docker Hub repository.
 

@@ -22,7 +22,7 @@ This includes:
 
 - The resources in the [Learning Center](/manuals/desktop/use-desktop/_index.md)
 - Pulling or pushing an image to Docker Hub
-- [Image Access Management](/manuals/security/for-developers/access-tokens.md)
+- [Image Access Management](/manuals/security/access-tokens.md)
 - [Static vulnerability scanning](/manuals/docker-hub/repos/manage/vulnerability-scanning.md)
 - Viewing remote images in the Docker Dashboard
 - Docker Build when using [BuildKit](/manuals/build/buildkit/_index.md#getting-started).

@@ -264,7 +264,7 @@ Each organization page now breaks down into these tabs:
 
 ### New features
 
-* You can now [create personal access tokens](/security/for-developers/access-tokens/) in Docker Hub and use them to authenticate from the Docker CLI. Find them in your account settings, under the new **[Security](https://hub.docker.com/settings/security)** section.
+* You can now [create personal access tokens](/security/access-tokens/) in Docker Hub and use them to authenticate from the Docker CLI. Find them in your account settings, under the new **[Security](https://hub.docker.com/settings/security)** section.
 
 ### Known Issues
 

diff --git a/content/manuals/enterprise/enterprise-deployment/_index.md b/content/manuals/enterprise/enterprise-deployment/_index.md
@@ -6,6 +6,30 @@ keywords: msi, docker desktop, windows, installation, mac, pkg, enterprise
 params:
   sidebar:
     group: Enterprise
+grid:
+- title: MSI installer
+  description: Learn how to install Docker Desktop with the MSI installer.
+  link: /enterprise/enterprise-deployment/msi-install-and-configure/
+- title: PKG installer
+  description: Learn how to install Docker Desktop with the PKG installer.
+  link: /enterprise/enterprise-deployment/pkg-install-and-configure/
+- title: MS Store
+  description: Learn how to install Docker Desktop through the Microsoft Store.
+  link: /enterprise/enterprise-deployment/ms-store/
+- title: Deploy with Intune
+  description: Learn how to deploy Docker Desktop on Windows and macOS devices using Microsoft Intune.
+  link: /enterprise/enterprise-deployment/use-intune/
+- title: Deploy with Jamf Pro
+  description: Learn how to deploy Docker Desktop for Mac using Jamf Pro
+  link: /enterprise/enterprise-deployment/use-jamf-pro/
+- title: Docker Desktop for Microsoft Dev Box
+  description: Install Docker Desktop for Microsoft Dev Box via the Microsoft Azure Marketlplace
+  link: /enterprise/enterprise-deployment/dev-box/
+- title: FAQs
+  description: Common questions when deploying Docker Desktop 
+  link: /enterprise/enterprise-deployment/faq/
 ---
 
-Docker Desktop supports scalable deployment options tailored for enterprise IT environments. Whether you're rolling out Docker across hundreds of developer workstations or enforcing consistent configuration through MDM solutions like Intune or Jamf, this section provides everything you need to install, configure, and manage Docker Desktop in a secure, repeatable way. Learn how to use MSI and PKG installers, configure default settings, control updates, and ensure compliance with your organization's policies—across Windows, macOS, and Linux systems.
+Docker Desktop supports scalable deployment options tailored for enterprise IT environments. Whether you're rolling out Docker across hundreds of developer workstations or enforcing consistent configuration through MDM solutions like Intune or Jamf, this section provides everything you need to install, configure, and manage Docker Desktop in a secure, repeatable way. Learn how to use MSI and PKG installers, configure default settings, control updates, and ensure compliance with your organization's policies—across Windows, macOS, and Linux systems.
+
+{{< grid >}}