Skip to content

[docs-scanner] Unclear explanation of SSO condition for company owner seat occupancy #24282

@docker-agent

Description

@docker-agent

File: content/manuals/admin/faqs/company-faqs.md

Issue

The FAQ about company owners occupying seats includes an unclear condition:

Company owners do not occupy a seat unless one of the following is true:

  • They are added as a member of an organization under your company
  • SSO is enabled

The second bullet point "SSO is enabled" lacks important context:

  1. Where is SSO enabled? (Company level? Organization level? Specific organization?)
  2. Why does SSO being enabled cause a seat to be occupied? (Does the owner need to sign in via SSO? Is it automatic?)
  3. Which company owners are affected? (All of them? Only those who use SSO?)

The same unclear statement appears in content/manuals/admin/company/owners.md as an Important callout, suggesting this is a documentation-wide gap rather than a typo.

Suggested fix

Expand the explanation to clarify the SSO condition. For example:

Company owners do not occupy a seat unless one of the following is true:

- They are added as a member of an organization under your company
- SSO is enabled for the company and the owner signs in using SSO (this automatically adds them as a member)

Or provide a link to more detailed documentation about how SSO affects company owner seat allocation.


Found by nightly documentation freshness scanner

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions