File: content/manuals/enterprise/security/hardened-desktop/settings-management/configure-admin-console.md
Issue
The documentation contains contradictory statements about whether Docker Home policies override local admin-settings.json files:
In configure-admin-console.md, the tip states:
You can upload an existing admin-settings.json file to pre-fill the form. Docker Home policies override local admin-settings.json files.
However, in _index.md, the policy precedence section states:
- User-specific policies: Highest priority
- Organization default policy: Applied when no user-specific policy exists
- Local
admin-settings.json file: Lowest priority, overridden by Docker Home policies
This creates confusion because:
- The tip in
configure-admin-console.md makes an absolute statement that "Docker Home policies override local admin-settings.json files"
- The precedence list in
_index.md shows that local admin-settings.json is "Lowest priority, overridden by Docker Home policies"
Both seem to say the same thing, but the phrasing in the tip could mislead readers into thinking Docker Home policies always override local files, when in fact the precedence list shows that user-specific policies and organization default policies from Docker Home override the local file, but the local file is still part of the precedence chain.
Why this matters
Administrators reading configure-admin-console.md might conclude that any Docker Home policy will override their local admin-settings.json file, when the actual behavior is more nuanced based on the policy precedence order. This could lead to incorrect deployment strategies or troubleshooting difficulties when settings don't behave as expected.
Suggested fix
Clarify the tip in configure-admin-console.md to align with the precedence order documented in _index.md. For example:
You can upload an existing admin-settings.json file to pre-fill the form. Docker Home policies (both user-specific and organization default) take precedence over local admin-settings.json files according to the policy precedence order.
Or simplify to:
You can upload an existing admin-settings.json file to pre-fill the form. Note: Docker Home policies take precedence over local admin-settings.json files.
Found by nightly documentation quality scanner
File:
content/manuals/enterprise/security/hardened-desktop/settings-management/configure-admin-console.mdIssue
The documentation contains contradictory statements about whether Docker Home policies override local
admin-settings.jsonfiles:In
configure-admin-console.md, the tip states:However, in
_index.md, the policy precedence section states:This creates confusion because:
configure-admin-console.mdmakes an absolute statement that "Docker Home policies override localadmin-settings.jsonfiles"_index.mdshows that localadmin-settings.jsonis "Lowest priority, overridden by Docker Home policies"Both seem to say the same thing, but the phrasing in the tip could mislead readers into thinking Docker Home policies always override local files, when in fact the precedence list shows that user-specific policies and organization default policies from Docker Home override the local file, but the local file is still part of the precedence chain.
Why this matters
Administrators reading
configure-admin-console.mdmight conclude that any Docker Home policy will override their localadmin-settings.jsonfile, when the actual behavior is more nuanced based on the policy precedence order. This could lead to incorrect deployment strategies or troubleshooting difficulties when settings don't behave as expected.Suggested fix
Clarify the tip in
configure-admin-console.mdto align with the precedence order documented in_index.md. For example:Or simplify to:
Found by nightly documentation quality scanner