Skip to content

fix: settings management moved in AC UI #22399

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 9, 2025
Merged

fix: settings management moved in AC UI #22399

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions content/manuals/security/for-admins/hardened-desktop/settings-management/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,10 +25,11 @@ For an extra layer of security, you can also use Settings Management to enable a
## How does it work?

You can configure several Docker Desktop settings using either:

- An `admin-settings.json` file. This file is located on the Docker Desktop host and can only be accessed by developers with root or administrator privileges.
- Creating a settings policy in the Docker Admin Console
- Creating a settings policy in the Docker Admin Console.

Settings that are defined by an administrator override any previous values set by developers and ensure that these cannot be modified.
Settings that are defined by an administrator override any previous values set by developers and ensure that these cannot be modified.

## What features can I configure with Settings Management?

Expand Down
2 changes: 1 addition & 1 deletion ...ecurity/for-admins/hardened-desktop/settings-management/compliance-reporting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@ This opens the Desktop settings reporting page. From here you can:

1. Sign in to the [Admin Console](https://app.docker.com/admin).
2. Select your organization or company from the **Choose profile** page.
3. Under Docker Desktop, select **Reporting**. By default, non-compliant users
3. Under **Docker Desktop**, select **Reporting**. By default, non-compliant users
are displayed.
4. Optional. Select the **Hide compliant users** checkbox to show both compliant
and non-compliant users.
Expand Down
9 changes: 5 additions & 4 deletions ...rity/for-admins/hardened-desktop/settings-management/configure-admin-console.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,9 +20,9 @@ organization for configurations to take effect.

## Create a settings policy

1. Within the [Docker Admin Console](https://admin.docker.com/) navigate to the company or organization you want to define a settings policy for.
2. Under the **Security and access** section, select **Desktop Settings Management**.
3. In the top-right corner, select **Create a settings policy**.
1. Within the [Docker Admin Console](https://app.docker.com/admin) navigate to the company or organization you want to define a settings policy for.
2. Under the **Docker Desktop** section, select **Settings Management**.
3. Select **Create a settings policy**.
4. Give your settings policy a name and an optional description.

> [!TIP]
Expand Down Expand Up @@ -68,7 +68,8 @@ If your settings policy needs to be rolled back, either delete the policy or edi

## Settings policy actions

From the **Actions** menu on the **Desktop Settings Management** page in the Docker Admin Console, you can:
From the **Actions** menu on the **Settings Management** page in the Docker Admin Console, you can:

- Edit or delete an existing settings policy.
- Export a settings policy as an `admin-settings.json` file.
- Promote a policy that is applied to a select group of users, to be the new global default policy for all users.