Skip to content

docs(orgs-and-teams): document collaborators and SSO as mutually exclusive [EDU-1513] - #1829

Merged
justinegeffen merged 4 commits into
masterfrom
docs/EDU-1513-collaborators-sso
Sep 14, 2026
Merged

justinegeffen merged 4 commits into
masterfrom
docs/EDU-1513-collaborators-sso

Conversation

@justinegeffen

Copy link
Copy Markdown
Contributor

What

Collaborators authenticate outside an organization's identity provider, so the platform blocks the combination in both directions. Neither doc set said so, and the remediation for the second case is not obvious from the error alone.

  • While SSO is active for an organization, adding a new collaborator to a workspace fails. Existing collaborators and existing organization members are unaffected — the guard only fires when a new organization membership would be created with the collaborator role.
  • While an organization has collaborators, SSO cannot be configured or activated. The fix is to remove the collaborator participants and add those users as organization members with email addresses matching the SSO domain.

Adds a Collaborators and SSO subsection to the Collaborators section, and the corresponding message to the participant error table.

Scope

Cloud, Enterprise, and the version-26.1 Enterprise snapshot. The Cloud page links to the single sign-on page; Enterprise has no equivalent organization-level SSO page to link to, so the term is left unlinked there.

Stacked PR

Based on the branch for #1828, which introduces the Collaborators content and the error table this builds on. Please review and merge that one first — this will retarget to master automatically.

Verification

Both directions of the guard were confirmed against the backend source, including the exact error message and the condition under which it fires. docusaurus build passes with no broken links. Vale reports 0 errors on the changed pages.

🤖 Generated with Claude Code

justinegeffen and others added 2 commits September 8, 2026 20:58
…EDU-26]

Adding a workspace participant by username or email can create both an
organization membership and a workspace participant record, and the two
usage limits that govern them are checked at different points. Neither
doc set explained this, so the members-per-organization limit appeared
to be hit for no reason.

Document what each starting state produces, which limit applies when,
and who gets notified. Clarify that having a Seqera account is not the
same as belonging to the organization, which is the distinction that
determines whether a member seat is consumed. Add the participant
troubleshooting messages, the default Launch role, and the collaborator
lifecycle in the Collaborators section.

For Enterprise, document TOWER_PARTICIPANT_AUTO_CREATE_USER and
TOWER_MEMBER_AUTO_CREATE_USER, including that accounts created on add
are marked as trusted regardless of the trusted email configuration.

Also fix the Collaborators cross-link, which pointed at workspace
creation rather than participant addition, and drop a stray code fence
in the Cloud page.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…usive [EDU-1513]

Collaborators authenticate outside the organization's identity provider,
so the platform blocks the combination in both directions: a new
collaborator cannot be added while SSO is active, and SSO cannot be
configured while any collaborators exist. Neither doc set said so, and
the remediation for the second case is not obvious.

Add a Collaborators and SSO subsection and the corresponding participant
error message.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@justinegeffen justinegeffen added the 1. Dev/PM/SME Needs a review by a Dev/PM/SME label Sep 8, 2026

@christopher-hakkaart christopher-hakkaart left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor editorial suggestion.

Comment thread platform-cloud/docs/orgs-and-teams/organizations.md Outdated
Comment thread platform-enterprise_docs/orgs-and-teams/organizations.md Outdated
Comment thread platform-enterprise_versioned_docs/version-26.1/orgs-and-teams/organizations.md Outdated
Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io>
Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>

@swingingsimian swingingsimian left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@justinegeffen justinegeffen added do not merge Do not merge until this label is removed 3. Dev/PM/SME reviews complete SMEs have reviewed and approved. and removed 1. Dev/PM/SME Needs a review by a Dev/PM/SME do not merge Do not merge until this label is removed labels Sep 10, 2026
Base automatically changed from docs/EDU-26-participant-creation-logic to master September 14, 2026 17:12
Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
@netlify

netlify Bot commented Sep 14, 2026 •

Copy link
Copy Markdown

❌ Deploy Preview for seqera-docs failed. Why did it fail? →

Name Link
🔨 Latest commit 4752f2a
🔍 Latest deploy log https://app.netlify.com/projects/seqera-docs/deploys/6aa849203d100500082a639b

@justinegeffen
justinegeffen merged commit c0084dd into master Sep 14, 2026
3 of 7 checks passed
@justinegeffen
justinegeffen deleted the docs/EDU-1513-collaborators-sso branch September 14, 2026 19:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3. Dev/PM/SME reviews complete SMEs have reviewed and approved.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants