Organizations: add IdP federation, remove Enterprise-only badge, fix sub-org nesting depth#32076
Merged
Merged
Conversation
…sub-org nesting depth - Remove <Plan type="enterprise" /> badge from index.mdx (Orgs supports both Enterprise and MSSP/Distributor) - Add IdP federation bullet to Core features list on index.mdx - Add IdP federation paragraph to policy-sharing.mdx intro - Add IdP federation to Share policies section on for-enterprise.mdx and for-mssp-distributors.mdx - Fix sub-org nesting depth from 2 tiers to 5 levels on for-mssp-distributors.mdx and limitations.mdx
Contributor
Review💡 2 suggestions found in commit Fix in your agentFix the following review findings in PR #32076 (https://github.com/cloudflare/cloudflare-docs/pull/32076).
Before making changes, review each finding and present a brief summary table:
- For each finding, state whether you agree, disagree, or need clarification
- If you disagree (e.g. the fix requires disproportionate effort for minimal benefit,
or the finding is factually incorrect), explain why
- If you need clarification before deciding, ask those questions
- Then share your plan for which issues to tackle and in what order
After triaging, fix all legitimate findings. For any you decide to skip,
post a comment on this PR with the finding ID and your reasoning.
---
## Style Guide Review
### Suggestions (2)
#### SG-ca746b2c8a45 · Single-digit numerals in body text should be spelled out
- **File:** `src/content/docs/fundamentals/organizations/for-mssp-distributors.mdx` line 56
- **Issue:** Line adds `up to 5 levels of nested sub-organizations`
- **Fix:** Spell out the numeral: `up to five levels of nested sub-organizations`
#### SG-f8cc9a6c158d · Spell out single-digit numerals in body text
- **File:** `src/content/docs/fundamentals/organizations/index.mdx` line 68
- **Issue:** Line adds `MSSP/Distributor Organizations support up to 5 levels of nested sub-organizations.`
- **Fix:** Spell out the numeral: `MSSP/Distributor Organizations support up to five levels of nested sub-organizations.`
Code ReviewThis code review is in beta and may not always be helpful — use your judgment. No code review issues found. ConventionsNo convention issues found. Style Guide ReviewSuggestions (2)
CommandsOnly codeowners can run commands. Post a comment with the command to trigger it.
|
Contributor
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
…o' section - Update MSSP hierarchy diagrams in index.mdx and for-mssp-distributors.mdx to show nested sub-organizations (3 tiers) - Add '5 levels of nested sub-organizations' note under the hierarchy diagram on index.mdx - Add nesting capability to Key characteristics on for-mssp-distributors.mdx - Remove 'Nested sub-organizations' from 'What you cannot do' section (it is a supported capability, not a limitation)
Standardize on 'automatically provisioned or removed as accounts join or leave the Organization' (matching policy-sharing.mdx) instead of the slightly different phrasing used on for-enterprise.mdx and for-mssp-distributors.mdx.
Contributor
|
Nimbus Preview URL: https://nimbus-5bb39e15.preview.developers.cloudflare.com |
Contributor
AdamBouhmad
reviewed
Jul 14, 2026
| | Adding existing accounts | Assigning existing accounts is not available for MSSP/Distributor Organizations. Use account creation to add new accounts. | | ||
| | Account creation | MSSP Organizations can self-serve create new customer accounts within their Organization. | | ||
| | Sub-Organizations | Distributors can create child MSSP Organizations. MSSP Organizations cannot create their own child Organizations — the hierarchy is limited to two tiers: Distributor → MSSP Organizations. | | ||
| | Sub-Organizations | Distributors can create child MSSP Organizations. MSSP/Distributor Organizations support up to 5 levels of nested sub-organizations. | |
Collaborator
There was a problem hiding this comment.
not blocking, but I imagine customers will want to get a sense of what defines a distributor/MSSP vs Enterprise, as that'll dictate the feature sets they will be offered today(i.e sub-orgs). I think this question is more relevant for enterprise customers, since MSSP/Distributors have to explicit engage with cloudflare to enroll in the program and should know they're in that cohort
AdamBouhmad
reviewed
Jul 14, 2026
|
|
||
| Policy sharing works the same way for both [Enterprise](/fundamentals/organizations/for-enterprise/) and [MSSP/Distributor](/fundamentals/organizations/for-mssp-distributors/) Organizations. | ||
|
|
||
| In addition to WAF and Gateway policies, Organizations supports [IdP federation](/cloudflare-one/integrations/identity-providers/idp-federation/), which lets you configure a single identity provider (such as Okta or Entra ID) in one account and share it across all accounts in your Organization. Shared IdP connections are read-only in recipient accounts and are automatically provisioned or removed as accounts join or leave the Organization. |
Collaborator
There was a problem hiding this comment.
not blocking, but wondering if there's an easy way to share features associated across cohorts versus replicating feature descriptions. Maybe a feature matrix? regardless totally fine if we go this route
AdamBouhmad
approved these changes
Jul 14, 2026
AdamBouhmad
left a comment
AdamBouhmad
left a comment
Collaborator
There was a problem hiding this comment.
left a few non-blocking comments, LGTM otherwise!
Contributor
Author
|
Thank you! I'm doing another update with a feature release on Friday, i'll include these comments then so this can go out |
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.
Changes
This PR makes the following updates to the Organizations public documentation:
1. Remove incorrect "Enterprise-only" badge (
index.mdx)The
<Plan type="enterprise" />component rendered an "Enterprise-only" badge at the top of the Organizations landing page. This is incorrect — Organizations is available to both Enterprise and MSSP/Distributor customers (as the page body already states). Removed the component.2. Add IdP federation to Core features (
index.mdx)Added a new bullet for IdP federation to the Core features list, linking to the IdP federation docs.
3. Add IdP federation to Policy sharing page (
policy-sharing.mdx)Added a paragraph after the intro explaining that Organizations also supports IdP federation for sharing identity provider configurations across accounts.
4. Add IdP federation to Enterprise page (
for-enterprise.mdx)Added IdP federation mention in the "Share policies" section.
5. Add IdP federation to MSSP/Distributors page (
for-mssp-distributors.mdx)Added IdP federation mention in the "Share policies" section.
6. Fix sub-organization nesting depth (
for-mssp-distributors.mdx,limitations.mdx)MSSP/Distributor Organizations now support up to 5 levels of nested sub-organizations. Updated the "What you cannot do" section and the limitations table which previously stated the hierarchy was limited to two tiers.
References