.webp)
Heartbeat monitors are now team-scoped. Teams can own their heartbeats, and access is controlled by the same RBAC configuration that governs the rest of Rootly On-Call—so a team member from one group can no longer view or modify another team’s monitors.
Why it matters
In multi-team environments, RBAC boundaries are what allow different engineering groups to operate independently without stepping on each other. Heartbeats were the last On-Call feature that didn’t respect those boundaries—any user with edit permissions could touch any team’s monitors, regardless of their role.
For enterprise customers running strict access-control configurations, this was a meaningful gap:
- Teams couldn’t trust that their heartbeat configuration was protected from modification by other groups
- Admins had no way to delegate heartbeat ownership to a specific team without exposing org-wide access
- It created friction during security reviews, where full RBAC isolation is often a hard requirement
How it works
When creating or editing a heartbeat, team admins can now assign an owning team. Access to that heartbeat—read, write, and delete—is then governed by the user’s On-Call role permissions for that team, consistent with how alerts, schedules, escalation policies, and alert sources already behave.
Getting started
No migration required. Existing heartbeats can be assigned to a team from the heartbeat settings page. New heartbeats created by team admins will default to their team as the owner.
Check out the docs to learn more.
