Skip to main content
Most issues resolve with one of the fixes below. If yours doesn’t, contact your Rootly account team.

​
Quick Fixes

​
If It Refuses a Request

Refusals are usually deliberate scope, not failures. Rootly AI’s native tools do not touch production systems, page through third-party vendors, write code, or change external platform configuration. A connector can expose separately governed external actions; see its connector guide for the exact tools and permissions. The full list of native limits lives at What Rootly AI Can’t Do.

​
Good to Know

  • Times render in your team’s time zone. Ask for UTC, your own time zone, or any IANA zone and Rootly AI converts.
  • Rootly AI in Web is read-only by design; Rootly-native write actions live in Slack incident channels and mobile, while supported connector actions follow their own surface and permission rules.
  • Rootly AI on Mobile takes incident updates such as status and severity, confirming with you before anything runs. Paging and status page publishing stay in Slack.
  • If your role recently changed, sign out of Slack and back in so Rootly AI picks up your current identity.
  • Tenant isolation is enforced by design. Rootly AI never surfaces incidents from teams you don’t belong to.

Rootly AI in Slack

What Rootly AI in Slack is and everything it can do.

Getting Started

Turn on Rootly AI in Slack and walk through your first interaction.

What to Use Rootly AI For

The full catalog of prompts, grouped by use case.

Data Privacy for Rootly AI

What Rootly AI sees, retention, and model training controls.