# How IncidentHub Teams Work

IncidentHub Teams give you a seamless way of managing independent sets of monitors, channels, and public status pages from the same IncidentHub account. 

Each Team in IncidentHub has its own set of

1. Monitored services.
2. Alert configuration - component filters, lifecycle filters, outage/maintenance toggle.
3. Notification channels.
4. Availability dashboard.
5. Public status page and configuration.

## Teams are Independent Sub-Accounts

In an IncidentHub account, monitored service configurations in one Team do not affect another Team even if they monitor the same services.

E.g. Team A can monitor Amazon Web Services  EC2 in us-east-1 and Team B monitors Amazon Web Services EC2 in us-central-1 in the same IncidentHub account.

This table shows a limited list of features to demonstrate how this separation extends to everything:

<table data-full-width="false"><thead><tr><th width="116">Team</th><th width="127">Channels</th><th>Services</th><th width="139">Alerting Configuration</th><th width="133">Maintenance Reminders</th><th>Public Status Page</th></tr></thead><tbody><tr><td>Platform Engineering</td><td>Slack #platform-team</td><td>EC2 us-east-1, Jenkins, Docker Hub</td><td>All alerts, Outages</td><td>On, 10 hours before</td><td>Password protected</td></tr><tr><td>Infra Engineering</td><td>Slack #infra-team</td><td>EC2 us-central-1, Terraform Cloud</td><td>All alerts, Outages and Maintenance</td><td>On, 12 hours before</td><td>Password protected</td></tr><tr><td>Customer Support</td><td>BoldDesk</td><td>HubSpot</td><td>Start/End only, Outages</td><td>Off</td><td>Whitelabeled branding and domain, password protected</td></tr></tbody></table>

## Switching Between Teams

Use the dropdown on the left navigation bar to switch between your Teams.

<figure><img src="https://1097519083-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1UERJeGV9Jx1B0oddXCx%2Fuploads%2Fe80nSRcbmZUxxkhvrEQG%2FScreenshot%20from%202026-04-06%2014-21-27.png?alt=media&#x26;token=90823b81-7425-49dd-b0ec-09894dfd5948" alt=""><figcaption></figcaption></figure>

Switching to a different Team changes the context of the other links on the sidebar. E.g. if you switch from Team A to Team B, your Dashboard, Availability, Status page will all point to Team B's settings.

## Team Service and Channel Limits

The maximum number of service monitors and channels you can add depends on your IncidentHub plan. In Teams-enabled IncidentHub accounts, the maximum for your account is calculated based on your usage across all teams.

E.g. if your plan has 300 service monitors and 20 channel integrations, and you have 6 teams, the total usage is based on the number of services and channels you add across all 5 teams.

<table><thead><tr><th width="236">Team</th><th width="238">Service Monitors</th><th width="219">Channel Integrations</th></tr></thead><tbody><tr><td>Customer Support</td><td>10</td><td>1</td></tr><tr><td>Data Infrastructure Platform</td><td>25</td><td>1</td></tr><tr><td>Product Engineering</td><td>30</td><td>2</td></tr><tr><td>Security Team</td><td>17</td><td>1</td></tr><tr><td>Marketing</td><td>14</td><td>1</td></tr><tr><td>Staging Platform</td><td>22</td><td>1</td></tr><tr><td>Account Usage</td><td>118/300</td><td>7/10</td></tr></tbody></table>

There is no individual limit for monitors and integrations within a team except the account limit.

You can see your current overall usage as well as the current team's usage on the bottom left of the sidebar.

<figure><img src="https://1097519083-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1UERJeGV9Jx1B0oddXCx%2Fuploads%2FCNNN5LZBo4kXYkL3F5bD%2FScreenshot%20from%202026-04-07%2010-22-35.png?alt=media&#x26;token=cc1356b7-3851-4451-8b7b-747fcb0f0db8" alt=""><figcaption></figcaption></figure>

## When to Use Teams

Some common use cases for Teams

1. When you have separate Teams in your organization who wish to monitor services, have different notification channels - e.g. Platform Engineering, Security, Data Infrastructure, etc. In this case, do a one-to-one mapping for your organization's teams to IncidentHub Teams.
2. When you wish to route different groups of service alerts to different channels. E.g. send alerts for services critical to your business to PagerDuty, and non-critical services to Slack. In this case, create one Team for each group and add the services you need in each. Set up PagerDuty in the first and Slack in the second.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.incidenthub.cloud/incidenthub-documentation/teams/how-incidenthub-teams-work.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.