Cases requirements
editCases requirements
editYou can create roles and define feature privileges at different levels to manage feature access in Kibana. Kibana privileges grant access to features within a specified Kibana space, and you can grant full or partial access. For more information, refer to Kibana privileges.
To send cases to external systems, you need the appropriate license.
If you are using an on-premises Kibana deployment and want the email notifications and the external incident management systems to contain links back to Kibana, you must configure the server.publicBaseUrl setting.
Certain subscriptions and privileges might be required to manage case attachments. For example, to add alerts to cases, you must have privileges for managing alerts.
To grant access to cases, set the privileges for the Cases and Actions and Connectors features as follows:
| Action | Kibana Privileges |
|---|---|
Give full access to manage cases and settings |
Roles without All privileges for the Actions and Connectors feature cannot create, add, delete, or modify case connectors. By default, All for the Cases feature allows you to delete cases, delete alerts and comments from cases, and edit case settings. You can customize the sub-feature privileges to limit feature access. |
Give assignee access to cases |
All for the Cases feature under Security Before a user can be assigned to a case, they must log into Kibana at least once, which creates a user profile. |
Give view-only access for cases |
Read for the Security feature and All for the Cases feature You can customize the sub-feature privileges to allow access to deleting cases, deleting alerts and comments from cases, and viewing or editing case settings. |
Revoke all access to cases |
None for the Cases feature under Security |