> ## Documentation Index > Fetch the complete documentation index at: https://docs.aciona.me/llms.txt > Use this file to discover all available pages before exploring further. # Organizations > Organization settings, data isolation and child organizations. The organization is aciona.me's isolation boundary. No data crosses it: teams, services, schedules, alert sources, incidents and notifications belong to exactly one organization. ## Settings Under **Settings**, owners and admins define: * **Organization name** — shown in the dashboard and in notifications sent to the team. * **Members and roles** — who participates and what each person can do. * **Channel integrations** — Slack and Microsoft Teams. * **Plan and subscription** — root organization owner only. ## Child organizations An organization can have child organizations, in a single level of hierarchy — there are no grandchildren. Use child organizations when you need **genuine data isolation** between units: an agency operating for different clients, a group with separate companies, an operation where teams must not see each other's incidents. Do not use them when separating by **team** would do. Teams already give you separation of responsibility inside the same organization, with far less duplicated configuration. **The plan belongs to the tenant, not to the child.** The subscription, billing profile and usage counters always belong to the **root** organization. Limits on members, teams, alert sources and incidents per month are summed across the root and all children. Only the **owner** of the root organization can create child organizations and manage the subscription. ## Data isolation Every request to aciona.me carries one organization's context. The product: * Never accepts an organization identifier from a webhook body — it is always inferred from the alert source. * Restricts queries and actions to the current organization. * Keeps incidents, alerts and notifications separated per organization.