Changelog

April 9, 2026

Keep Rootly in sync with Google Workspace.

Keep Rootly in sync with Google Workspace.

Google Directory Sync connects Rootly directly to the Google Admin Directory API and keeps your organization in sync automatically. Users are provisioned when they're added to Google Workspace, deprovisioned when they're suspended or deleted, and their phone numbers—critical for on-call routing—are synced along with their profiles. Groups can be selectively mapped to Rootly Groups with automatic role assignment based on membership.

Why it matters

On-call teams need accurate membership data to route pages correctly. A stale roster means missed pages, incorrect escalations, and on-call engineers who no longer work at the company. Google Directory Sync closes that gap by keeping Rootly continuously aligned with your source of truth:

How it works

Google Directory Sync polls the Google Admin Directory API to detect changes. Unlike SCIM, which relies on push events from an identity provider, this approach requires no webhook configuration—Rootly pulls the latest state on a schedule. A mass deletion safeguard prevents accidental bulk deprovisioning if the API returns partial results, and a full audit log tracks every sync operation.

Two authentication options are available: OAuth for simpler setup, or service account with domain-wide delegation for enterprise environments with stricter admin policies.

Getting started

  1. Navigate to Integrations in your Rootly dashboard and find Google Directory Sync.
  2. Choose your authentication method—OAuth or service account—and connect your Google Workspace admin account.
  3. Configure group sync and role assignment, then trigger an initial manual sync to validate the connection.

Check out the docs to learn more and get started.

With Google Directory Sync, your Rootly organization stays current automatically—so your on-call coverage reflects who's on your team, automatrically.

What else shipped

Improvements

On-Call

  • Heartbeats can now be scoped to individual teams, giving team admins ownership and visibility over their own monitors without exposing org-wide configuration.
  • Alert description text containing angle brackets (e.g. <cluster-name>) now displays correctly instead of being silently dropped.
  • Generic webhook alert sources now display the configured source name in Slack alert blocks instead of showing "Generic Webhook".

Incident Response

  • The timeline_updated workflow trigger now exposes the triggering event in the Liquid context, enabling workflows to act on specific timeline entries.
  • Retrospective documents now export images correctly to Notion.
  • Retrospective templates using Atlassian markdown now render correctly in Confluence exports instead of displaying plain text.
  • The incident closed_at timestamp now records when the incident was actually closed, not when it was resolved.
  • Incident types can now be deleted from the Catalog UI.
  • The Zoom meeting session options menu now displays consistently without requiring the user to join the meeting first.
  • Zoom meeting transcript sessions now correctly display participant names after the session ends.
API

Incident Response

  • The filter[search] parameter on the GET /v1/users endpoint now correctly filters results by name or email.
  • Team-scoped API keys can now access the GET /v1/oncalls endpoint.
MCP Server
  • Runtime security dependencies updated to address newly disclosed vulnerabilities, including fastmcp, cryptography, and Pygments.
Fixes

On-Call

  • Fixed an RBAC regression where users could view and select alert sources from other teams when creating alert routes.
  • Fixed escalation policy path routing for API-created alerts using alert fields with time restrictions.
  • Fixed alert grouping rules not applying to alerts from certain third-party monitoring sources.
  • Fixed a schedule rotation display bug where certain handoff times appeared as 12:00 AM.
  • Live Call Routing no longer incorrectly resolves an alert when the caller hangs up.
  • Fixed the Slack alert block layout for triggered alerts—title format, icon placement, and paging section position now match design spec.

Incident Response

  • Fixed the "Convert to Incident" Slack modal on Enterprise Grid not advancing to the incident form after workspace selection.
  • Fixed status page subscription verification links returning 404 on custom domains.
  • Fixed the default incident Slack announcement not updating when an incident is resolved via a workflow action.
  • Fixed Slack block workflows with "Send only as threaded message" enabled being ignored when triggered from a Slack command.
  • Fixed Backstage integration URLs returning authentication errors on the integrations page.
  • Fixed the Owning Team dropdown showing all groups in the organization instead of only groups the current user belongs to.
  • Fixed team managers without global heartbeat permissions being unable to create new heartbeats.

You and your teams deserve
modern incident management.

Get a 1:1 demo with one of our technical staff or start your free 14-day trial.