Elastic Docs ›Kibana Guide ›Stack Management ›Cases
« Cases Open and manage cases »

Configure access to casesedit

This functionality is in technical preview and may be changed or removed in a future release. Elastic will apply best effort to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.

To access cases in Stack Management, you must have the appropriate Kibana privileges:

Action Kibana privileges

Give full access to manage cases
  • All for the Cases feature under Management.
  • All for the Actions and Connectors feature under Management.

The Actions and Connectors feature privilege is required to create, add, delete, and modify case connectors and to send updates to external systems.

By default, All for the Cases feature includes authority to delete cases and comments unless you customize the sub-feature privileges.

Give assignee access to cases

All for the Cases feature under Management.

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 Cases feature under Management.

Give access to view and delete cases

Read for the Cases feature under Management with the deletion sub-feature enabled.

Revoke all access to cases

None for the Cases feature under Management.

For more details, refer to Kibana privileges.

If you are using an on-premises Kibana deployment and you want the email notifications and the external incident management systems to contain links back to Kibana, you must configure the server.publicBaseUrl setting.

« Cases Open and manage cases »