> ## 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.

# Create your organization

> The first step: the isolated space where teams, services, schedules and incidents live.

The organization is the container for everything in aciona.me. Teams, services, schedules, alert sources and incidents belong to one organization and are never visible to another.

## Creating one

<Steps>
  <Step title="Create your account">
    Sign up at [aciona.me](https://aciona.me) and confirm your email.
  </Step>

  <Step title="Name the organization">
    Use your company or business unit name — it is what your team sees at the top of the dashboard and in notifications.
  </Step>

  <Step title="You become the owner">
    Whoever creates the organization gets the **owner** role: full control, including billing and creating child organizations.
  </Step>
</Steps>

## One organization or several?

Start with **one**. Most teams never need more.

Child organizations make sense when you need genuine data isolation between units — an agency operating for different clients, or a group with separate companies.

<Note>
  The plan and its limits (teams, members, sources, incidents per month) belong to the **root** organization and are shared by it and all of its children. Only the root owner manages the subscription.
</Note>

## Switching organizations

If you belong to more than one organization, the dashboard lets you switch between them. Each switch changes the entire context: the incidents, teams, services and schedules shown all become that organization's.

<Card title="Next: invite members" icon="user-plus" horizontal href="/en/getting-started/invite-members" />