> ## 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 first team

> The team is the unit of responsibility: it links services to on-call schedules.

In aciona.me an alert is never delivered "to the company". It is delivered to a **team**, and from there to whoever is on call for that team.

## Creating one

<Steps>
  <Step title="Open Teams and create a new one">
    Give it a name that reflects real responsibility: `Platform`, `Backend`, `SRE`, `Data`, `Checkout`.
  </Step>

  <Step title="Add members">
    Only team members can be part of that team's on-call schedule.
  </Step>

  <Step title="Link services">
    Every monitored service needs a responsible team. You can make that link here or from the services screen.
  </Step>
</Steps>

## How to shape your teams

<AccordionGroup>
  <Accordion title="Start with few teams" icon="minimize-2">
    One team per area that actually carries a pager. Too many teams up front produces empty schedules and ownerless alerts.
  </Accordion>

  <Accordion title="One team per responsibility, not per org chart" icon="git-branch">
    If the same five people answer for the API, the database and the queues at 3 a.m., that is one team — even if the org chart says three.
  </Accordion>

  <Accordion title="Every team that owns a service needs a schedule" icon="calendar-clock">
    A team without an active schedule has nobody on call. The incident is created, but ends up with no owner.
  </Accordion>
</AccordionGroup>

<Card title="Next: create a service" icon="server" horizontal href="/en/getting-started/create-service" />