Repository navigation
Clarify how SSO, IdP Managed Access, and SCIM fit together - #421
Open
claude[bot] wants to merge 9 commits into
Open
claude[bot] wants to merge 9 commits into
claude[bot] wants to merge 9 commits into
Conversation
- Add an overview and comparison table of SSO, IdP Managed Access, SCIM, and Teams, plus a numbered setup checklist, and reorder the SSO page to follow it - Document that subdomains must be claimed separately - Explain how SCIM maps IdP groups to Teams (create-or-link, and that deleting a group deletes the Team) on the SSO, Okta, and Azure pages - Add an "Enter Your IdP Details in Mixpanel" step and a Troubleshooting section - Fix OneLogin, Google Workspace, and JumpCloud guidance, and small typos Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
 [Low impact] This documentation update appears safe to merge. Reviews (7) · Last reviewed commit: "Merge branch 'main' into claude/sso-setu..." · Reviewed by Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
…ds on IdP settings Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… in SSO doc Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Single Sign-On: update the SSO/IdP Managed Access/SCIM comparison table, note that Shared SSO manages these settings in the Admin Organization, drop "beta" from the Shared SSO reference, and convert setup steps, IdP provider list, and troubleshooting to Steps, CardGroup, and AccordionGroup. - Shared SSO: align SCIM-to-Teams wording with the main SSO page, merge the two Azure warnings, remove a duplicate Team membership paragraph, use "IdP" consistently, link to the SSO setup steps, and convert the migration list to Steps. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Document that just-in-time provisioning can't be turned on in an Admin Organization or its linked organizations, so users must be provisioned with SCIM or invited from Mixpanel. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Use a numbered list for Setup Steps and the Shared SSO migration steps, replace the IdP CardGroup with a comparison table, add a OneLogin subsection, and restore the Microsoft provisioning tutorial link. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
kurbycchua
marked this pull request as ready for review
November 13, 2026 05:53
kurbycchua
enabled auto-merge (squash)
November 13, 2026 05:53
This branch was successfully deployed
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
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.
Requested by Kurby Chua · Slack thread
Before: The SSO page described SSO, IdP Managed Access, just-in-time provisioning, and SCIM as separate settings without explaining how they relate, and its sections didn't follow the order you set things up in. It didn't say that subdomains need to be claimed separately. The Okta and Azure pages said to give an IdP group the same name as a Mixpanel Team and to set the Organization Role on the Team, which doesn't match how group push works. A few provider notes were out of date (G-Suite naming, OneLogin, JumpCloud links).
After: The SSO page opens with what each piece does and a table comparing SSO only, SSO + IdP Managed Access, and SSO + IdP Managed Access + SCIM, followed by a numbered setup checklist that the rest of the page now follows. It explains that subdomains are matched exactly and must be claimed on their own, adds a step for entering the IdP's certificate and URLs in Mixpanel, explains how SCIM links or creates Teams from IdP groups (and that deleting a group deletes the Team), and adds a short Troubleshooting section. The Okta and Azure pages describe the same group-to-Team behavior. All existing anchors that other pages link to still work.
How: Edited
docs/access-security/single-sign-on.mdx(restructure and new sections),single-sign-on/okta.mdxandsingle-sign-on/azure.mdx(Teams behavior, Push Groups, delete warning, typo and copy-paste fixes),single-sign-on/jumpcloud.mdx(link the general setup page),single-sign-on/google.mdx(current tab name), andlogin-methods.mdx(SSO summary). Frontmatter and link checks inscripts/pass.Generated by Claude Code