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:

Team	Channels	Services	Alerting Configuration	Maintenance Reminders	Public Status Page
Platform Engineering	Slack #platform-team	EC2 us-east-1, Jenkins, Docker Hub	All alerts, Outages	On, 10 hours before	Password protected
Infra Engineering	Slack #infra-team	EC2 us-central-1, Terraform Cloud	All alerts, Outages and Maintenance	On, 12 hours before	Password protected
Customer Support	BoldDesk	HubSpot	Start/End only, Outages	Off	Whitelabeled branding and domain, password protected

Switching Between Teams

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

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.

Team	Service Monitors	Channel Integrations
Customer Support	10	1
Data Infrastructure Platform	25	1
Product Engineering	30	2
Security Team	17	1
Marketing	14	1
Staging Platform	22	1
Account Usage	118/300	7/10

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.

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.

When Not to Use Teams

1. If you are an MSP or an agency who wants to give your clients a unique status page that shows the services from their stack only, the Per-client status pages is a better fit. You can use it by signing up for the Multi-client plan.