- Observability: other versions:
- What is Elastic Observability?
- What’s new in 8.7
- Send data to Elasticsearch
- Spin up the Elastic Stack
- Deploy Elastic Agent to send data
- Deploy Beats to send data
- Elastic Serverless Forwarder for AWS
- Deploy serverless forwarder
- Configuration options
- Troubleshooting
- Observability overview page
- Application performance monitoring (APM)
- Application logs
- Log monitoring
- Infrastructure monitoring
- Uptime
- Synthetics (beta)
- Get started
- Scripting browser monitors
- Configure lightweight monitors
- Manage monitors
- Analyze monitor data
- Monitor resources on private networks
- Use the CLI
- Configure projects
- Configure Synthetics settings
- Grant users access to secured resources
- Manage data retention
- Use Synthetics with traffic filters
- Migrate from the Elastic Synthetics integration
- User Experience
- Universal Profiling
- Alerting
- Cases
- CI/CD observability
- Troubleshooting
- Fields reference
- Tutorials
- Monitor Amazon Web Services (AWS) with Elastic Agent
- Monitor Amazon Web Services (AWS) with Beats
- Monitor Google Cloud Platform
- Monitor a Java application
- Monitor Kubernetes
- Monitor Microsoft Azure with Elastic Agent
- Monitor Microsoft Azure with the native Azure integration
- Monitor Microsoft Azure with Beats
Configure access to cases
editConfigure access to cases
editTo access and send cases to external systems, you need the appropriate license, and your role must have the Cases Kibana privilege as a user for the Observability feature.
Here are the minimum required privileges:
| Action | Kibana Privileges |
|---|---|
Give full access to manage cases |
Roles without |
Give assignee access to cases |
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 |
|
Give access to view and delete cases |
These privileges also enable you to delete comments and alerts from a case. |
Revoke all access to cases |
|
If you are using an on-premises Kibana deployment and want your email notifications and external incident management systems to contain links back to Kibana, configure the server.publicBaseUrl setting.
For more details, refer to feature access based on user privileges.
