> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sreagent.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Run parent and child organizations

> Create child organizations, mirror members, copy configuration, and understand what a child inherits.

export const Plan = ({tier}) => <Badge color="blue">{tier} plan</Badge>;

<Plan tier="Enterprise" />

A parent organization can create children, for example one per client or business unit. Org admins of an organization that is not itself a child see an **Organizations** card at the top of **Settings**. Click **Open** to reach the **Organizations** page.

<Steps>
  <Step title="Create a child">
    Under **Create a new child**, enter a **Name** and **Slug** and click **Create**. You become the
    child's org admin automatically. A counter shows how many of your plan's children you have used.
  </Step>

  <Step title="Mirror members">
    Under **Mirror members**, tick people from the parent, tick the children, choose a **Role** and
    click **Mirror**. People already in a child keep their role unless you tick **Overwrite existing
    role**. You cannot mirror anyone in above your own role. Mirrored people are marked as coming
    from the parent.
  </Step>

  <Step title="Copy configuration">
    Under **Copy configuration**, pick a **Kind**: alert routes, outbound rules, prompt templates,
    notification settings, deploy policies, synthetic checks, runbooks or organization settings.
    Tick the rows and the children, then click **Copy**. Each row passes the same checks as if you
    typed it into the child, and the result lists what was created or skipped. A copy belongs to the
    child from then on. A copied runbook arrives as an unapproved draft with its connector targeting
    cleared, and a copied prompt template is never made the child's default.
  </Step>

  <Step title="Switch into a child">
    Click **Switch** on a child's row if you are a member there.
  </Step>
</Steps>

## What a child inherits

A child reads its parent's Slack workspace, GitHub installation, AI providers and outbound paging targets until it configures its own, and saving one locally overrides it. Its **Settings** and **Integrations** pages name the parent on each inherited card, and the **Overrides** column on the parent's page shows what each child has overridden.

A child also uses the parent's plan, quotas and AI budget. Its **Subscription** page says so and offers nothing to buy. Monthly counters, seats and synthetic checks are pooled across the family, and each person counts once. Connectors, data sources, automations and remote agents stay per organization.

## Unlink a child

SRE Agent support links an existing organization as a child and unlinks one, on request. The effects are immediate:

* Inherited settings stop resolving through the former parent. A child's outbound rule that used a parent target is disabled, not deleted.
* Mirrored members are removed unless you name exceptions to keep, which are then marked as formerly from the parent. A child always keeps at least one admin.
* The child returns to its own plan, or to Free.
* Incidents already paged through the parent's target stay open there. Resolve them in that provider.

## Related

* [Choose a plan and manage billing](/guides/administer/plans-and-billing): how a child uses its parent's plan.
* [Limits](/guides/reference/limits): child organization limits.
* [Manage people and roles](/guides/administer/organizations-and-roles): roles inside each organization.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.