Repository navigation
docs(cloud): document child organizations - #1279
Conversation
Add the Child Organizations guide and link it from Organization Management and Navigating Organizations. Signed-off-by: Cooper Fitzgerald <182300328+fitzergerald@users.noreply.github.com>
|
Yay, your first pull request! 👍 A contributor will be by to give feedback soon. In the meantime, please review the Layer5 Community Welcome Guide and sure to join the community Slack. |
|
Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configuration
📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
🟡 Changes recommended
It documents undeployed UI and overstates or introduces unsupported membership and form capabilities.
3 open findings
What changed in this PR
Documents hierarchical child organizations in Layer5 Cloud.
Changes:
- Adds child-organization creation, permissions, administration, and deletion guidance.
- Links the guide from organization management and navigation documentation.
| File | Description |
|---|---|
child-organizations.md |
Adds the new guide. |
_index.md |
Adds a child-organizations overview. |
navigating-organizations.md |
Links to the new guide. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
|
||
| ## Child Organizations | ||
|
|
||
| An Organization can have child Organizations of its own, to any depth. A child is created from the **Child organizations** section of the Organizations page, and an Organization Administrator or Owner of the parent can edit the child's settings and membership, or delete it, without joining the child. Anything inside the child still requires membership in the child. Deleting an Organization that still has children is refused until the children are deleted. See [Child Organizations](child-organizations/) for details. |
| tags: [orgs] | ||
| --- | ||
|
|
||
| A **child organization** is an organization created inside another organization, called its **parent**. A child is otherwise an ordinary organization: it has its own members, teams, workspaces, invitations, domain, and credentials. The parent relationship adds one thing, which is that administrators of the parent can manage the child's settings and membership from the parent. |
| 2. Go to the Organizations page and find the **Child organizations** section. | ||
| 3. Use the create control in that section and fill in the same details you provide for any organization: name, country, region, and description. |
|
🚀 Preview deployment: https://docs.layer5.io/pr-preview/pr-1279/
|
Summary
cloud/guides/organizations/org-management/child-organizations.md: nesting with no depth limit under the single provider organization, who can create (Create Organization in the parent) and see (View Organizations in the parent) children, what a parent Organization Administrator or Owner can do from the parent (edit settings, add and search members, delete a childless child) and cannot do (workspaces, environments, connections, credentials, teams, identity providers, mail server), refusal to delete an organization that has children, no reparenting, and switcher behavior.Source: layer5io/meshery-cloud
docs/plans/2026-09-25-hierarchical-organizations-implementation.mdon master.Test plan
hugosite build completes with no warningsSummary by CodeRabbit