Skip to content

Commit

Permalink
[8.1] [BUG] Document required Security privs for cases (backport #3261)…
Browse files Browse the repository at this point in the history
… (#3291)

Co-authored-by: Lisa Cawley <[email protected]>
Co-authored-by: Nastasha Solomon <[email protected]>
Co-authored-by: nastasha.solomon <[email protected]>
  • Loading branch information
4 people authored May 17, 2023
1 parent d26336e commit e298337
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions docs/getting-started/cases-req.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -10,10 +10,10 @@
You can create roles and define feature privileges at different levels to manage feature access in {kib}. {kib} privileges grant access to features within a specified {kib} space, and you can grant full or partial access. For more information, see
{kibana-ref}/xpack-spaces.html#spaces-control-user-access[Feature access based on user privileges].

NOTE: To send cases to external systems, you need the
https://www.elastic.co/subscriptions[appropriate license].
IMPORTANT: Certain subscriptions and privileges might be required to manage case attachments. For example, to add alerts to cases, you must have privileges for <<enable-detections-ui,managing alerts>>. To send cases to external systems, you need the
https://www.elastic.co/subscriptions[appropriate license].

To grant access to cases, set the {kib} space privileges for the *Cases* and *Actions and Connectors* features as follows:
To grant access to cases, set the {kib} space privileges for the *Cases* and *{connectors-feature}* features as follows:

[discrete]
[width="100%",options="header"]
Expand Down

0 comments on commit e298337

Please sign in to comment.