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

# Teams

> Organize your responders into teams for streamlined incident management and escalations

## Overview

Teams are the foundation of your incident response structure. By grouping responders into teams, you can efficiently manage on-call rotations, assign incidents, and configure escalation policies. Teams make it easy to notify the right people when incidents occur.

<CardGroup cols={2}>
  <Card title="Organized Response" icon="sitemap">
    Group responders by function, expertise, or responsibility area
  </Card>

  <Card title="Escalation Ready" icon="arrow-up-right-dots">
    Use teams as targets in escalation policies for group notifications
  </Card>
</CardGroup>

***

## Why Use Teams?

<Tabs>
  <Tab title="Incident Routing">
    Route incidents to the right group of people automatically:

    * **By Service** — Database Team, API Team, Frontend Team
    * **By Region** — EMEA Support, APAC Support, Americas Support
    * **By Expertise** — Security Team, Performance Team, Infrastructure Team

    When an incident is assigned to a team, all members can see and respond to it.
  </Tab>

  <Tab title="Escalation Policies">
    Teams integrate seamlessly with escalation policies:

    * Add entire teams as escalation targets
    * Notify all team members simultaneously
    * Combine with individual users and schedules
    * Configure parallel or sequential notification

    This ensures incidents reach the right people even during complex escalation flows.
  </Tab>

  <Tab title="On-Call Management">
    Teams work together with schedules for on-call rotations:

    * Define who's available to respond
    * Set up rotation schedules within teams
    * Assign default escalation policies
    * Track team availability
  </Tab>
</Tabs>

***

## Viewing Teams

The Teams page displays all teams in your organization:

| Column      | Description                           |
| ----------- | ------------------------------------- |
| **Team**    | Team name and description             |
| **Members** | Number of members with avatar preview |
| **Status**  | Active or Inactive                    |
| **Created** | When the team was created             |
| **Actions** | Edit, manage members, or delete       |

### Filtering Teams

Use the toolbar to find specific teams:

* **Search** — Filter by team name or description
* **Status Filter** — Show All, Active only, or Inactive only

***

## Creating Teams

<Steps>
  <Step title="Open Create Dialog">
    Click the **Create Team** button in the top right corner
  </Step>

  <Step title="Enter Team Details">
    Fill in the team information: - **Name** — Display name for the team (e.g.,
    "Platform Engineering") - **Slug** — Unique identifier, lowercase with
    hyphens (e.g., `platform-engineering`) - **Description** — Brief explanation
    of the team's responsibility
  </Step>

  <Step title="Save the Team">Click **Create** to save your new team</Step>
</Steps>

<Info>
  The slug is auto-generated from the team name but can be customized. It's used
  in URLs and integrations.
</Info>

### Slug Format

The slug must follow these rules:

* Lowercase letters only
* Numbers allowed
* Hyphens for spaces
* No special characters

**Examples:**

* `backend-api`
* `customer-support-tier1`
* `devops-infrastructure`

<Warning>
  The slug cannot be changed after creation. Choose a meaningful, permanent
  identifier.
</Warning>

***

## Managing Team Members

### Viewing Members

Team members are shown in the Members column with avatar previews:

* Up to 4 avatars displayed
* "+X" indicator shows additional members
* Click the members cell to open the full member list

### Adding Members

<Steps>
  <Step title="Open Members Dialog">
    Click the **three-dot menu** (⋮) and select **Manage Members**, or click
    directly on the members cell
  </Step>

  <Step title="Select User">
    Use the dropdown to find the user you want to add
  </Step>

  <Step title="Add to Team">
    Click the **Add** button to add them to the team
  </Step>
</Steps>

The member is added immediately and can start receiving notifications for team-assigned incidents.

### Removing Members

<Steps>
  <Step title="Open Members Dialog">
    Click the three-dot menu and select **Manage Members**
  </Step>

  <Step title="Find the Member">Locate the member in the list</Step>
  <Step title="Remove">Click the **X** button next to their name</Step>
</Steps>

<Note>
  Removed members will no longer receive notifications for incidents assigned to
  this team.
</Note>

### Member Information

The members dialog shows:

* **Avatar** — User's profile picture or initials
* **Name** — Full name
* **Email** — Contact email address
* **Phone** — Phone number (if configured)

***

## Member Roles

Each team member can have one of two roles:

| Role       | Description                                  |
| ---------- | -------------------------------------------- |
| **Lead**   | Team leader with management responsibilities |
| **Member** | Standard team member                         |

<Tip>
  Member roles are informational and help identify team structure. Both roles
  receive the same notifications.
</Tip>

***

## Editing Teams

To modify an existing team:

<Steps>
  <Step title="Find the Team">Locate the team in the list</Step>

  <Step title="Open Edit Dialog">
    Click the **three-dot menu** (⋮) and select **Edit**
  </Step>

  <Step title="Update Information">Modify the team name or description</Step>
  <Step title="Save Changes">Click **Save** to apply your modifications</Step>
</Steps>

<Note>
  The team slug cannot be changed after creation. If you need a different slug,
  create a new team and migrate members.
</Note>

***

## Deactivating vs. Deleting Teams

### Deactivating Teams

Deactivate a team to temporarily disable it while preserving its configuration:

1. Edit the team
2. Set status to **Inactive**
3. Save changes

**Inactive teams:**

* Won't appear in escalation target selections
* Members remain associated
* Can be reactivated at any time
* Historical data preserved

### Deleting Teams

Delete a team to permanently remove it:

<Steps>
  <Step title="Open Delete Dialog">
    Click the **three-dot menu** (⋮) and select **Delete**
  </Step>

  <Step title="Confirm Deletion">
    Read the warning and click **Delete** to confirm
  </Step>
</Steps>

<Warning>
  Deleting a team removes all member associations and cannot be undone. Consider
  deactivating instead if you might need the team again.
</Warning>

***

## Teams in Escalation Policies

Teams are powerful targets for escalation policies, allowing you to notify multiple responders at once.

### Adding Teams to Escalations

When configuring an escalation policy:

1. Add a new level or edit existing
2. Select **Team** as the target type
3. Choose the team from the dropdown
4. Configure notification channels

### Notification Behavior

When a team is notified through an escalation:

<CardGroup cols={2}>
  <Card title="Parallel Mode" icon="arrows-split-up-and-left">
    All team members are notified simultaneously. First responder handles the
    incident.
  </Card>

  <Card title="Sequential Mode" icon="arrow-down-1-9">
    Team members are notified one by one until someone acknowledges.
  </Card>
</CardGroup>

### Mixed Targets

Escalation levels can combine different target types:

* Individual users
* Teams
* On-call schedules

This flexibility allows complex notification flows tailored to your organization.

<Accordion title="Example: Multi-Level Escalation">
  **Level 1** (0 min):

  * On-Call Schedule: "Primary On-Call"

  **Level 2** (5 min):

  * Team: "Backend Engineering"
  * Mode: Parallel

  **Level 3** (15 min):

  * User: "Engineering Manager"
  * Team: "Leadership"

  This ensures the on-call person is notified first, then the entire team if no response, and finally leadership for critical situations.
</Accordion>

***

## Common Team Structures

<AccordionGroup>
  <Accordion title="By Technical Domain">
    Organize teams by area of expertise:

    * **Backend Team** — API and server-side services
    * **Frontend Team** — Web and mobile applications
    * **Infrastructure Team** — Cloud and DevOps
    * **Database Team** — Data storage and optimization
    * **Security Team** — Security incidents and compliance
  </Accordion>

  <Accordion title="By Service Ownership">
    Align teams with services they own:

    * **Payments Team** — Payment processing service
    * **Auth Team** — Authentication and authorization
    * **Notifications Team** — Email, SMS, push services
    * **Search Team** — Search and indexing service
  </Accordion>

  <Accordion title="By Support Tier">
    Structure for customer support escalations:

    * **Support Tier 1** — First-line support
    * **Support Tier 2** — Technical escalation
    * **Support Tier 3** — Engineering escalation
  </Accordion>

  <Accordion title="By Region">
    Global teams for follow-the-sun support:

    * **EMEA Team** — Europe, Middle East, Africa
    * **APAC Team** — Asia Pacific
    * **Americas Team** — North and South America
  </Accordion>
</AccordionGroup>

***

## Best Practices

<AccordionGroup>
  <Accordion title="Keep Teams Focused">
    Each team should have a clear responsibility area. Avoid creating catch-all teams that include everyone—they become noise rather than signal.
  </Accordion>

  <Accordion title="Right-Size Your Teams">
    Teams should be large enough to provide coverage but small enough that members feel ownership. 5-10 members is often ideal for on-call teams.
  </Accordion>

  <Accordion title="Use Descriptive Names">
    Team names should clearly indicate their purpose:

    **Good:** "Payment Processing Team", "EU Customer Support"

    **Avoid:** "Team A", "Engineers", "Support"
  </Accordion>

  <Accordion title="Document Team Purpose">
    Use the description field to explain:

    * What services/areas the team owns
    * When to escalate to this team
    * Team lead or contact person
  </Accordion>

  <Accordion title="Regular Membership Reviews">
    Periodically review team membership:

    * Remove people who've left or changed roles
    * Add new team members promptly
    * Verify contact information is current
  </Accordion>

  <Accordion title="Integrate with Escalations">
    Don't create teams in isolation. Plan how they'll be used in escalation policies to ensure proper incident routing.
  </Accordion>
</AccordionGroup>

***

## Troubleshooting

<AccordionGroup>
  <Accordion title="Team members not receiving notifications">
    1. Verify the team is set to **Active**
    2. Check that members have valid contact methods configured
    3. Confirm the team is properly added to the escalation policy
    4. Verify the escalation policy is assigned to the service
  </Accordion>

  <Accordion title="Can't find a team in escalation dropdown">
    1. Check if the team is set to **Active** (inactive teams don't appear)
    2. Refresh the page to load latest teams
    3. Verify you have permission to view teams
  </Accordion>

  <Accordion title="Can't add a user to the team">
    1. Verify the user exists in your organization
    2. Check if they're already a member (they won't appear in dropdown)
    3. Ensure you have write permission for teams
  </Accordion>

  <Accordion title="Slug already exists error">
    Each team slug must be unique within your organization. Choose a different slug or modify the existing team instead.
  </Accordion>

  <Accordion title="Can't delete a team">
    Check if the team is referenced in:

    * Active escalation policies
    * Incident assignments

    Remove these references before deleting, or deactivate the team instead.
  </Accordion>
</AccordionGroup>

***

## Teams vs. Groups

Teams and Groups serve different purposes in EasyAlert:

| Aspect       | Teams                                       | Groups                            |
| ------------ | ------------------------------------------- | --------------------------------- |
| **Purpose**  | Incident response and escalations           | Access control and permissions    |
| **Used For** | On-call, incident assignment, notifications | Role assignment, feature access   |
| **Found In** | Escalation policies, incidents              | User management, IAM              |
| **Members**  | Responders for specific services            | Users needing similar permissions |

<Tip>
  Use **Teams** for operational structure (who responds to incidents) and
  **Groups** for access control (who can do what in the platform).
</Tip>