Skip to content

Desktop Settings Management in different location #22398

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.

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

Closed
1 task done
steilerDev opened this issue Apr 9, 2025 · 1 comment · Fixed by #22399
Closed
1 task done

Desktop Settings Management in different location #22398

steilerDev opened this issue Apr 9, 2025 · 1 comment · Fixed by #22399
Assignees
Labels
status/triage Needs triage

Comments

@steilerDev
Copy link

Is this a docs issue?

  • My issue is about the documentation content or website

Type of issue

Information is incorrect

Description

Point 2 of "Create a settings policy" instructs

Under the Security and access section, select Desktop Settings Management.

This seems to have moved and is now under the Docker Desktop section.

Location

https://docs.docker.com/security/for-admins/hardened-desktop/settings-management/configure-admin-console/

Suggestion

Under the Docker Desktop section, select Settings Management.

@steilerDev steilerDev added the status/triage Needs triage label Apr 9, 2025
@sarahsanders-docker sarahsanders-docker self-assigned this Apr 9, 2025
@sarahsanders-docker sarahsanders-docker linked a pull request Apr 9, 2025 that will close this issue
1 task
@sarahsanders-docker
Copy link
Collaborator

Thanks for flagging @steilerDev! Working on this fix now :)

sarahsanders-docker added a commit that referenced this issue Apr 9, 2025
## Description
- Settings management has moved, this PR fixes this. I will update the
UI tests as well

## Related issues or tickets
- #22398

## Reviews
- [ ] Editorial review
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/triage Needs triage
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants