Team Management

FireHydrant teams allow you to quickly assign the right group of people to an incident from your chat application or the FireHydrant UI. You can use FireHydrant Teams to:

• Automatically assign responders to incidents based on various criteria, including impacted infrastructure, tags, and any other incident parameter
• Organize and see which team owns which components throughout your infrastructure
• Automatically assign on-call responders from your alerting provider to an incident

Create and edit teams

To create and manage teams:

1. Go to Teams (or Settings > Teams, if you do not have Signals enabled.

2. Click "+ Add team" on the right side of the page if creating, or directly click on the team whose settings you'd like to edit.

3. There are several different fields you can configure and set on Teams:

   1. Name - The team name

   2. Description - A longer description for the team

   3. Slug - The slug for the team. This will be automatically generated from the team name if left blank

   4. Slack Channel (Signals-only) - The designated Slack channel for the team. This allows notifications for things like coverage requests to be posted to the team's Slack channel. This setting is only visible for users with Signals enabled.

   5. Microsoft Teams Channel (Signals-only) - The designated Microsoft Teams channel for the team. Like for Slack, this allows for things like coverage request notifications to be posted directly to the team. This setting is only visible for users with Signals enabled.

   6. Memberships - The list of team members and their default roles** when assigned to incidents. Memberships can also link directly with on-call schedules from Signals or 3rd-party alerting providers.

      

   7. Services for incident response - Teams can be configured as responders for Services and Functionalities in FireHydrant. This allows automatically assigning teams to incidents when components are marked as impacted.

   8. Services owned - Teams can be set as owners for several components and settings throughout FireHydrant, including Services. See the section below on component ownership.

4. Once finished, click "Save" or "Create team" to persist changes.

📘

**Note:

FireHydrant provides default Incident Roles, but you can configure roles however you like. FireHydrant also allows automating team assignments using SSO and SCIM.

Assigning on-call users from alerting providers

FireHydrant supports assigning users to roles from on-call schedules directly within teams if you are using a 3rd-party alerting provider. These are the providers FireHydrant supports:

• Opsgenie
• PagerDuty
• Splunk On-Call (VictorOps)

Once your chosen alerting provider is set up and configured, you should see your escalation policies, on-call schedules, or routing keys available in the dropdown when configuring team membership.

📘

Note:

To assign on-call users when using FireHydrant's Signals, we recommend the following two approaches:

• Assign a Role runbook step - On top of specific users, this Runbook step allows choosing Signals Escalation Policies and On-Call Schedules. When the step executes, it will dynamically look up whoever is on-call according to the chosen policy/schedule and assign them.
• Associating Teams in Service Catalog - When a Team is a responder to a Service/Functionality and it has a default escalation policy, FireHydrant will automatically look up who's on call in that EP when the Service/Functionality is impacted on an incident.

Component ownership

FireHydrant teams can own several components or objects throughout the FireHydrant platform. The default behavior is that anyone with Member permissions and higher can make edits to most settings in FireHydrant.

But when an owning team is set on an object, only members of that team can make updates to that object henceforth. FireHydrant supports team ownership for the following items:

• Runbooks
• Services and Functionalities
• Readiness Checklists

🚧

Note:

If someone sets an owning team on an object, and they are not part of that owning team, they will immediately lose edit access after clicking Save unless they have Owner permissions.

Next Steps

Once you have your teams configured, you can continue expanding your usage of FireHydrant:

• Learn about assigning users, teams, and roles to incidents
• Set up some Services or Functionalities in the Catalog and set the responding teams so that whenever an incident occurs, users always know which team(s) need to be involved for which services
• Learn more about setting up escalation policies, on-call schedules, and more with FireHydrant Signals