- Kibana Guide: other versions:
- What is Kibana?
- What’s new in 7.9
- Get started
- Set up Kibana
- Discover
- Dashboard
- Canvas
- Maps
- Machine learning
- Graph
- Visualize
- Observability
- Logs
- Metrics
- APM
- Uptime
- Elastic Security
- Dev Tools
- Stack Monitoring
- Stack Management
- Ingest Manager
- Reporting
- Alerting and Actions
- REST API
- Kibana plugins
- Accessibility
- Breaking Changes
- Release Notes
- Kibana 7.9.3
- Kibana 7.9.2
- Kibana 7.9.1
- Kibana 7.9.0
- Kibana 7.8.1
- Kibana 7.8.0
- Kibana 7.7.1
- Kibana 7.7.0
- Kibana 7.6.2
- Kibana 7.6.1
- Kibana 7.6.0
- Kibana 7.5.2
- Kibana 7.5.1
- Kibana 7.5.0
- Kibana 7.4.2
- Kibana 7.4.1
- Kibana 7.4.0
- Kibana 7.3.2
- Kibana 7.3.1
- Kibana 7.3.0
- Kibana 7.2.1
- Kibana 7.2.0
- Kibana 7.1.1
- Kibana 7.1.0
- Kibana 7.0.1
- Kibana 7.0.0
- Kibana 7.0.0-rc2
- Kibana 7.0.0-rc1
- Kibana 7.0.0-beta1
- Kibana 7.0.0-alpha2
- Kibana 7.0.0-alpha1
- Developer guide
IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Access agreement
editAccess agreement
editSome work environments require you to acknowledge and accept an agreement before you can access Kibana, which can contain sensitive information. The agreement text supports Markdown format and can be specified using the xpack.security.authc.providers.<provider-type>.<provider-name>.accessAgreement.message
setting.
You need to acknowledge the access agreement only once per session, and Kibana reports the acknowledgement in the audit logs.
Here is how your kibana.yml
can look like if you define an access agreement:
xpack.security.authc.providers: basic.basic1: order: 0 accessAgreement: message: "**You are accessing a system with a sensitive information** \n\n By logging in, you acknowledge that (shortened ...)"
When you authenticate using basic.basic1
, you’ll see the following agreement that you must acknowledge before you can access Kibana:

Was this helpful?
Thank you for your feedback.