Summary
Alerting v2 introduces four separate privileges in Kibana role management, listed under the Alerting category. Writers need to document what each privilege controls so that administrators can set up custom roles with the right level of access.
The four privileges are:
| Privilege |
All |
Read |
| Rules |
Create, edit, delete, enable, and disable rules |
View rules |
| Alerts |
Acknowledge, snooze, assign, tag, activate, and deactivate alert episodes |
View alert episodes |
| Action Policies |
Create, update, delete, snooze, and unsnooze action policies |
View action policies |
| Execution history |
View rule execution history |
View rule execution history |
Each privilege is independent — holding one does not grant another. For example, a user with Action Policies: All cannot create or edit rules, and a user with Rules: All cannot manage action policies.
Execution history is read-only at both levels; there is no write surface for execution history.
Resources
- PR #270574 — Introduces the Action Policies privilege as a standalone entry, separate from Rules
- PR #272440 — Introduces the Execution history privilege as a standalone entry, separate from Action Policies
Availability
| Channel |
Details |
| Stack |
v9.5.0 |
| Serverless |
~Jun 29–Jul 3 |
| Feature flag |
Alerting v2 preview |
Summary
Alerting v2 introduces four separate privileges in Kibana role management, listed under the Alerting category. Writers need to document what each privilege controls so that administrators can set up custom roles with the right level of access.
The four privileges are:
Each privilege is independent — holding one does not grant another. For example, a user with Action Policies: All cannot create or edit rules, and a user with Rules: All cannot manage action policies.
Execution history is read-only at both levels; there is no write surface for execution history.
Resources
Availability