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

# Incident types and lifecycles

> Let teams manage their own incident types and lifecycles

Give a team the **Manage incident types** permission (and **Manage incident lifecycles** for lifecycles) on a team role, so it only applies to the incident types and lifecycles that team owns.

Set an incident type's owner in the **Incident type owner** field at [**Settings → Incident Types**](https://app.incident.io/~/settings/incident-types), and a lifecycle's owner in the **Lifecycle owner** field at [**Settings → Respond → Lifecycle**](https://app.incident.io/~/settings/lifecycle). Once owned, only the owning team, or anyone with the permission account-wide, can change it.

These permissions are **not** in the **Standard** role, so a type or lifecycle with no owning team is managed only by people who hold the permission account-wide, exactly as today.

<Info>
  Your **default** lifecycle can't be owned by a team: it applies to every incident, so changes to it always need the
  account-wide permission.
</Info>

See [Team roles](/admin/team-roles) for the full setup.

## FAQs

<AccordionGroup>
  <Accordion title="Who can change which teams own an incident type?">
    Reassigning ownership always requires the **Manage incident types** permission granted account-wide. A team can
    manage the configuration of a type they own, but they can't hand it to another team or remove their own team from
    it.
  </Accordion>

  <Accordion title="What happens to incident types with no owning team?">
    Nothing changes for them. They can only be managed by people who hold the **Manage incident types** permission
    account-wide, the same as how every incident type behaves today.
  </Accordion>

  <Accordion title="Can a type be owned by more than one team?">
    Yes. You can assign multiple owning teams, and a member of any one of them (with the permission granted to that
    team) can manage the type.
  </Accordion>

  <Accordion title="What about incident forms?">
    Form overrides for a team-owned incident type follow that type's owning teams, so only the owning team can override
    or edit them. Organization-wide forms that aren't tied to a specific type still need the **Manage incident types**
    permission granted account-wide. See [Incident forms](/admin/incident-forms).
  </Accordion>

  <Accordion title="Can admins still manage every incident type and lifecycle?">
    Yes. Anyone who holds the permission account-wide can manage any incident type or lifecycle, regardless of which
    team owns it.
  </Accordion>
</AccordionGroup>