File: content/manuals/accounts/organization/manage/manage-licenses.md
Issue
The documentation contradicts itself about SSO and provisioning requirements. In manage-licenses.md, it states:
AI Governance licenses include single sign-on (SSO) and provisioning features regardless of your Docker Core subscription. Automatic license assignment requires setting up SSO, then provisioning with System for Cross-domain Identity Management (SCIM) or Just-in-Time (JIT).
However, in content/manuals/security/authentication/_index.md, it clearly states:
SSO requires a Docker Business subscription.
Why this matters
Readers trying to understand whether they can use SSO with AI Governance licenses alone (without a Business subscription) will get conflicting information. This affects purchasing decisions and setup expectations. If AI Governance truly provides SSO capabilities without Business, that's a significant feature that contradicts the general authentication documentation. If it doesn't, the manage-licenses.md text is misleading.
Suggested fix
Clarify the relationship between AI Governance licenses and SSO/provisioning features. Either:
- If AI Governance does provide SSO without Business: Update the authentication documentation to note this exception and explain the scope/limitations
- If AI Governance requires Business for SSO: Remove or rephrase the claim in manage-licenses.md to clarify that SSO setup (which requires Business) is a prerequisite for automatic license assignment, not a feature included with AI Governance
The text should make clear what subscription tier is actually required for SSO when using AI Governance.
Found by nightly documentation quality scanner
File:
content/manuals/accounts/organization/manage/manage-licenses.mdIssue
The documentation contradicts itself about SSO and provisioning requirements. In manage-licenses.md, it states:
However, in
content/manuals/security/authentication/_index.md, it clearly states:Why this matters
Readers trying to understand whether they can use SSO with AI Governance licenses alone (without a Business subscription) will get conflicting information. This affects purchasing decisions and setup expectations. If AI Governance truly provides SSO capabilities without Business, that's a significant feature that contradicts the general authentication documentation. If it doesn't, the manage-licenses.md text is misleading.
Suggested fix
Clarify the relationship between AI Governance licenses and SSO/provisioning features. Either:
The text should make clear what subscription tier is actually required for SSO when using AI Governance.
Found by nightly documentation quality scanner