Source
On-call schedules, rotations & escalation — found from sitemap — FireHydrant
Checked for FireHydrant on 6 Nov 2026
- Page
- https://docs.firehydrant.com/docs/signals-escalation-policies
- Checked
- 6 Nov 2026, 04:31 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:634e5dc3b07eb5ee0fc6a242f3250db229867b56ad12b7c00a38f3f0abe7a85c
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Escalation policy steps Report an error
“Every escalation policy has a set of steps that outlines who should be notified for an Alert and how long to wait between those steps.”
-
Escalation targets Report an error
“Most users will choose On-Call Schedules as targets for EP steps, but FireHydrant also allows directly notifying specific users and Slack channels.”
-
Empty schedule escalation Report an error
“If a given step targets an on-call schedule with no active shift or user on-call, FireHydrant will immediately escalate to the next step, even if a delay is configured on the next step.”
-
Escalation repeats handoff Report an error
“you can define a repetition that makes sense for the kinds of Alerts you are sending to the policy. After the repetitions are completed (if there are any), you can also define a hand-off, which will send the Alert to another escalation policy for the team, or you can send the Alert to another Team.”
-
Default escalation policy Report an error
“Each team can set one Escalation policy as its default policy, allowing any other team or user to send an Alert to that team directly.”
-
Escalation no self handoff Report an error
“An escalation policy cannot hand off to itself. You should configure Repeats instead.”
-
Step time to respond Report an error
“For each step, you can define a timeout period. This is the amount of time to wait for a response before escalating to the next step. This includes any delays that the user has defined in their notification preferences.”
-
Escalation targets team limited Report an error
“You must select a person or on-call schedule to notify each step. These notification targets will be limited to the team creating the escalation policy.”
-
Alert triggers to ep Report an error
“You can send Alerts to an escalation policy by creating an Alert Trigger and selecting an escalation policy as the notification target.”
-
Adhoc paging Report an error
“any user in your organization can send a page (i.e., create a one-off Alert) in Slack or in the web application. Those alerts can be sent to your Escalation policy.”
-
Page priority options Report an error
“When you send a page from the web application ("Send an Alert") or with the Slack /fh page command, you can choose a notification priority of High, Medium, or Low. The priority defaults to High”
-
Page entire team Report an error
“In cases where you need to page every member of a team in an instant, you can search for the team you'd like to page, and select the option under "Entire Team"”
-
Rbac escalation permissions Report an error
“Users with Member permissions can configure and update any escalation policies within any teams they are members of. Users with Owner permission can edit the same for all teams regardless of their membership or lack thereof.”
Scores citing this record
- The Engineering Manager On-call schedules, rotations & escalation
- The ICT Risk Officer On-call schedules, rotations & escalation
- The IT Operations Manager On-call schedules, rotations & escalation
- The MSP NOC Lead On-call schedules, rotations & escalation
- The MSP NOC Lead Integrations, API & administration
- The Skeptic On-call schedules, rotations & escalation
- The SRE Lead On-call schedules, rotations & escalation