Conversation
The provisioning overview had an unfocused title, a thin SEO description, long unwrapped lines, and an attribute list that mixed required and optional fields into prose. Retitle the page to 'User provisioning overview', expand the description and keywords, wrap body text at 80 characters, and move the SSO attributes into a table with a required column. Co-authored-by: Cursor <cursoragent@cursor.com>
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
The provisioning overview described each method in isolation, so readers could not tell that JIT overwrites SCIM attributes or that JIT wins over auto-provisioning on an SSO domain. Add a precedence list under the default setup, link each method from the comparison table, note that auto-provisioning only adds existing Docker accounts, and point to the provisioning troubleshooting page. Co-authored-by: Cursor <cursoragent@cursor.com>
Admins who enable SCIM while JIT is on by default had no canonical guidance on overwrite and removal risks, and related FAQs mixed SCIM with auto-provisioning. Put the recommended-source decision and both-enabled rules on the SCIM overview, then cross-link from JIT, SCIM setup, the provisioning overview, troubleshooting, and Security FAQs. Co-authored-by: Cursor <cursoragent@cursor.com>
aevesdocker
approved these changes
Sep 24, 2026
aevesdocker
left a comment
aevesdocker
left a comment
Contributor
There was a problem hiding this comment.
wording-wise, LGTM. 2 non-blocking nits
The SCIM pages described provisioning behavior inconsistently: the overview didn't explain how SCIM and JIT interact, group mapping didn't distinguish what SAML SSO sends at sign-in from what SCIM syncs on a schedule, and the setup and migration pages used stale Entra ID naming, mixed numbered-list styles, and long unwrapped lines. Rewrote the four SCIM pages for accuracy and consistency: added a section on choosing how SCIM works with JIT, separated the SSO and SCIM group-mapping paths, corrected the Okta and Microsoft Entra ID setup values and links, and normalized front matter, list numbering, and line wrapping. Co-authored-by: Cursor <cursoragent@cursor.com>
The provisioning docs said SCIM could not manage or deprovision users created through JIT or added manually, and they attributed removal and attribute conflicts to the wrong mechanism. Describe SCIM as able to link and deprovision members whose email domain is verified on the SSO connection, correct deactivation and team-sync behavior, and align the JIT and SCIM toggle steps with the UI. Co-authored-by: Cursor <cursoragent@cursor.com>
Resolve provisioning conflicts with the enforce-sign-in move and the dropped platform aliases. Address review wording: use you in the SSO FAQ, and tell readers to review how SCIM works with JIT before choosing a provisioning method. Co-authored-by: Cursor <cursoragent@cursor.com>
The JIT page linked group mapping to a heading that is not on the SCIM overview, and several provisioning pages had long unwrapped lines and numbered steps that did not all use 1. Wrap those pages, renumber the JIT flows, point the SCIM link at the setup page, and use the canonical Docker Team name in group mapping. Co-authored-by: Cursor <cursoragent@cursor.com>
This branch has not been 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
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.
Doc that adds some context about JIT vs SCIM, per SME resources. Makes updates to overview docs, troubleshooting, and FAQs. Also includes a freshness pass from tier 1 and tier 2 review agents.