[docs-scanner] Missing information about impact on already-signed-in users when enforcement is deployed

[docker-agent]

File: content/manuals/enterprise/security/enforce-sign-in/_index.md

Issue

The "How sign-in enforcement works" section explains what happens when users try to sign in after enforcement is enabled, but doesn't explain what happens to users who are already signed in to Docker Desktop when the enforcement configuration is deployed.

The current text states:

When Docker Desktop detects a registry key, .plist file, or registry.json file:

• A Sign in required! prompt appears, requiring users to sign in as organization members to use Docker Desktop.

This doesn't clarify:

• Whether users already signed in with non-organization accounts are immediately signed out
• Whether users already signed in with organization accounts continue working uninterrupted
• Whether the enforcement only takes effect after Docker Desktop restarts or after the user signs out
• Whether users need to restart Docker Desktop for the enforcement to be detected

Why this matters

Administrators planning a deployment need to know:

• Whether they should notify users to save their work before enforcement is deployed
• Whether enforcement will cause immediate disruption to active users
• What the user experience will be during the rollout
• Whether they need to schedule the deployment during off-hours

Without this information, administrators might deploy enforcement during business hours and cause unexpected disruption, or might unnecessarily schedule off-hours deployment when it's not needed.

Suggested fix

Add a note to the "How sign-in enforcement works" section explaining the impact on existing sessions. For example:

Note

When enforcement is first deployed, users already signed in to Docker Desktop will continue working until they sign out or restart Docker Desktop. At that point, they will see the Sign in required! prompt and must sign in with an organization member account to continue using Docker Desktop.

Or if the behavior is different (immediate sign-out), document that instead.

---

Found by nightly documentation quality scanner