Skip to content

Commit

Permalink
Add slight edits to the new section.
Browse files Browse the repository at this point in the history
  • Loading branch information
DonNateR committed Feb 24, 2021
1 parent 5f8e162 commit 660ccfc
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions docs/getting-started/detections-req.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -73,13 +73,13 @@ image::images/sec-admin-user.png[]
[[access-detections-ui]]
== Access and use Detections

After enabling Detections, only users with these permission can view and use the
*Detections* page:
After enabling Detections, only users with these permission can view and use rules and alerts on *Detections* page:

**All**

These permissions are required for both rule and alert management:

* {kib} space with `All` privileges enabled for `Security`.
* The `maintenance` permission for `.siem-signals-<kib-space>`.
* The `read`, `write`, and `view_index_metadata` index privileges for all of these system indices:
** `.lists-<kib-space>`
Expand All @@ -92,11 +92,11 @@ image::images/sec-user.png[]

**Rule**

For rule management, make sure {kib} space with `All` privileges enabled for both `Security` and `Saved Objects Management` features.
For rule management, make sure {kib} space with `All` privileges is enabled for both `Security` and `Saved Objects Management` features.

**Alert**

If you only want a user to be update the status of alerts but not rule, only {kib} space with `All` privileges enabled for `Security` is required.
If you only want a user to be update the status of alerts but not rule, only {kib} space with `All` privileges enabled for `Security` is required.


[discrete]
Expand Down

0 comments on commit 660ccfc

Please sign in to comment.