Clarification on Grafana IRM Users vs. Grafana Cloud Users Billing

Grafana Cloud Grafana IRM
2

Here’s the answer I got from GrotAI

Hi, I’m Grot.

Short answer:

  • There is no IRM-only identity separate from Grafana Cloud users. IRM uses (and syncs) the same organization users/teams from your Grafana Cloud stack; users appear in IRM after being added to Grafana Cloud and synced (up to every 30 minutes) (Users and teams).

  • Billing for IRM is based on monthly active IRM users, not merely on being a Grafana Cloud user. A user becomes an “active IRM user” if they’re on an on-call schedule or escalation chain, or if they take IRM actions like receiving/paging, changing alert group status, or creating/updating incidents (Check : Understand your IRM invoice).

What this means for you:

  • You won’t be billed twice “per person” just for having them as a Grafana Cloud user and also visible in IRM. IRM charges are tied to IRM active usage. Grafana Cloud has its own plan limits (for example, the Free plan lists “3 active users” as part of the stack benefits), but the provided sources don’t specify separate per-user billing for general dashboard access beyond plan limits. I’m sorry, but there’s no explicit source here detailing non-IRM user licensing mechanics beyond the plan descriptions.

  • To onboard someone only for IRM and limit broader Grafana access, add them as a Grafana Cloud user with the minimal org role (for example, Viewer) and then control IRM permissions via IRM RBAC and teams. IRM relies on org-level roles and can grant fine-grained IRM permissions without elevating their Grafana basic role (Users and teams → RBAC, Available RBAC roles, Manage teams in IRM). This ensures they only interact with alerts/incidents as needed.

  • To avoid IRM charges for a user, don’t include them in schedules/escalation chains and avoid IRM-active actions. Only users who meet “active IRM user” criteria count toward IRM billing (IRM active usage definition).

If you need strict separation across teams or customers, consider separate Grafana instancesacks for true isolation, but note the management/billing implications at the level (How to organize teams and resources).