Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion explore-analyze/alerts-cases/alerts/alerting-setup.md
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,11 @@ Likewise, you can customize the **Rules Settings** sub-feature privileges relate

To create a rule that uses the [Cases connector](kibana://reference/connectors-kibana/cases-action-type.md), you must also have `All` privileges for the **Cases** feature.

The rule type also affects the privileges that are required. For example, to create or edit {{ml}} rules, you must have `all` privileges for the **Analytics > {{ml-app}}** feature. For {{stack-monitor-app}} rules, you must have the `monitoring_user` role. For {{observability}} rules, you must have `all` privileges for the appropriate {{observability}} features. For Security rules, refer to [Detections prerequisites and requirements](../../../solutions/security/detect-and-alert/detections-requirements.md).
The rule type also affects the privileges that are required to create and edit rules. For example:
* For {{ml}} rules, you must have `all` privileges for the **Analytics > {{ml-app}}** feature.
* For {{stack-monitor-app}} rules, you must have the `monitoring_user` role.
* For most {{observability}} rules, you must have `all` privileges for the appropriate {{observability}} features. However, for a custom threshold rule, you only need the `stack alerts` privilege.
* For Security rules, refer to [Detections prerequisites and requirements](../../../solutions/security/detect-and-alert/detections-requirements.md).

::::

Expand Down
Loading