Clarify how users are provisioned under SAML#4202
Open
AmberAlston wants to merge 1 commit into
Open
Conversation
replicated-ci
added
type::docs
✅ Deploy Preview for replicated-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
✅ Deploy Preview for replicated-docs-upgrade ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Adds a "How users are added to your team under SAML" section that lays out the provisioning paths (SCIM, IdP-initiated JIT, domain-redirect JIT, email invitation) in a table, so admins on SAML-only teams know how a brand-new user gets created instead of hitting a dead end at the email-invite note. Also: - Rewrites the circular IdP-initiated login paragraph that said it "only works for existing and invited users" without explaining where new users come from. - Fixes a broken cross-reference that pointed at the SCIM section for a provisioning explanation it never gave. - Adds a Troubleshooting section documenting the user-facing login error "No SAML-enabled teams found for email domain" and its causes. - Links the SAML-only note on the team-management page to the new provisioning section. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
AmberAlston
force-pushed
the
saml-provisioning-docs-clarity
branch
from
f2b25d8 to
973db17
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Preview link: https://deploy-preview-4202--replicated-docs.netlify.app/vendor/team-management-saml-auth#provisioning-users-with-saml
What
Clarifies how new team members are added when a team uses SAML, especially under SAML-only enforcement. Today the docs tell admins that SAML-only teams don't use email invites, but never explain how a brand-new user (one who doesn't yet exist in the team) actually gets created. That gap leads to support escalations.
Changes
team-management-saml-auth.md, with a table covering the four provisioning paths: SCIM, IdP-initiated JIT, domain-redirect JIT, and email invitation. Defines JIT in plain terms and notes that domain redirect is enabled by Support / the account team rather than self-service.No SAML-enabled teams found for email domain, its causes, and the fix.team-management.mdto the new provisioning section.Verification done
The troubleshooting entry was checked against the backend. The error fires for a not-yet-existing user only when no SAML-enabled team has the user's email domain in its authorized domains. The doc wording matches that behavior.