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

# Core concepts

> Organization, member, team, service, on-call schedule, alert source, alert and incident.

aciona.me has few concepts, and they all fit on a single line: an **organization** has **members**, who form **teams**, which own **services**, covered by **on-call schedules**. External tools send **alerts** through **alert sources**, and alerts become **incidents**.

<AccordionGroup>
  <Accordion title="Organization" icon="building">
    Your company's isolated space. Every piece of data — teams, services, schedules, sources, incidents — belongs to one organization and is never visible to another.

    An organization can have child organizations (one per business unit, for example). The plan and its limits belong to the root organization and are shared across the group.

    [See organizations](/en/organizations/overview)
  </Accordion>

  <Accordion title="Member" icon="user">
    A person inside an organization, with a role: **owner**, **admin**, **member** or **viewer**. The role defines what they can configure and which incidents they can act on.

    [See roles and permissions](/en/organizations/roles-and-permissions)
  </Accordion>

  <Accordion title="Team" icon="users">
    The group of people responsible for a set of services. The team is the unit of responsibility: it connects services to on-call schedules.

    [See teams](/en/teams/overview)
  </Accordion>

  <Accordion title="Service" icon="server">
    What is being monitored: `payments-api`, `checkout`, `auth`, `erp-integration`. Each service has a responsible team and a default severity, used when the alert does not carry its own.

    [See services](/en/services/overview)
  </Accordion>

  <Accordion title="On-call schedule" icon="calendar-clock">
    Defines who is on call at any moment for a team: ordered participants, rotation type (weekly or 24x7), timezone and rotation start. Temporary overrides cover vacations, days off and one-off swaps.

    [See on-call](/en/on-call/schedules)
  </Accordion>

  <Accordion title="Alert source" icon="webhook">
    The entry point for an external tool. Each source has a type (Grafana, Prometheus, Datadog, CloudWatch, Zabbix, New Relic or generic webhook), a unique ingestion URL and a unique token.

    [See alert sources](/en/alert-sources/overview)
  </Accordion>

  <Accordion title="Alert" icon="bell-ring">
    The raw event arriving from the monitoring tool, with the original payload preserved. An alert can create an incident, be aggregated into an existing one, or resolve it.
  </Accordion>

  <Accordion title="Incident" icon="siren">
    aciona.me's unit of work: someone needs to look at this. It has severity, status, an owner, a timeline and a notification history.

    <Note>
      In Brazilian Portuguese the customer-facing term is *acionamento*. In English — and in every technical contract, such as routes, payload fields and enums — the term is `incident`.
    </Note>

    [See incidents](/en/incidents/lifecycle)
  </Accordion>
</AccordionGroup>

## How they connect

```mermaid theme={null}
flowchart TD
  Org["Organization"] --> Member["Members"]
  Org --> Team["Teams"]
  Org --> Service["Services"]
  Org --> Source["Alert sources"]
  Member --> Team
  Team --> Schedule["On-call schedule"]
  Service --> Team
  Source --> Alert["Alerts"]
  Alert --> Service
  Alert --> Incident["Incidents"]
  Schedule --> Incident
```

<Tip>
  Configure a single complete path — one team, one service, one schedule and one source — and the whole product already works end to end. Start with [Receive your first alert](/en/getting-started/first-alert).
</Tip>