# Kibana Space unable to access Observability functions

**URL:** <https://discuss.elastic.co/t/kibana-space-unable-to-access-observability-functions/343275>\
**Category:** Kibana\
**Tags:** elastic-stack-security\
**Created:** [September 18, 2023, 2:38pm UTC](https://discuss.elastic.co/t/kibana-space-unable-to-access-observability-functions/343275 "2023-09-18T14:38:54Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ryan\_Downey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ryan_downey/32/35987_2.png) [@Ryan\_Downey](https://discuss.elastic.co/u/Ryan_Downey)\
**Post date:** [September 18, 2023, 2:38pm UTC](https://discuss.elastic.co/t/kibana-space-unable-to-access-observability-functions/343275/1 "2023-09-18T14:38:54Z")

</div>

Elasticsearch and Kibana 7.17  
Support Team,

I'm looking to provide access to some of our users via a Space we'll call "autos". All I need this space to do is provide access to two different indices, logs-_-auto-_ and logs-_-_-auto-\*, and also be able to view all features in the Analytics and Observability sections of Kibana. Right now I've been able to provide access to the Analytics section but when I go to Observability I get the error message, "Contact your administrator. This integration is not yet enabled. Your administrator has the required permissions to turn it on." I do not get this error message for Analytics.

Users are accessing Kibana with SAML if that changes anything but it seems like theres something wrong with my privileges somewhere. Overall, I want users to be able to see their data but not make any changes to it so read access seems appropriate.

> GET \_security/role/autos-testing  
> {  
> "autos-testing" : {  
> "cluster" : ,  
> "indices" : [  
> {  
> "names" : [  
> logs-_-auto-_,  
> logs-_-_-auto-\*  
> ],  
> "privileges" : [  
> "read",  
> "view\_index\_metadata"  
> ],  
> "field\_security" : {  
> "grant" : [  
> "\*"  
> ],  
> "except" :   
> },  
> "allow\_restricted\_indices" : false  
> }  
> ],  
> "applications" : [  
> {  
> "application" : "kibana-.kibana",  
> "privileges" : [  
> "feature\_discover.read",  
> "feature\_dashboard.read",  
> "feature\_canvas.read",  
> "feature\_maps.read",  
> "feature\_ml.read",  
> "feature\_graph.read",  
> "feature\_visualize.minimal\_read",  
> "feature\_visualize.url\_create",  
> "feature\_logs.read",  
> "feature\_infrastructure.read",  
> "feature\_apm.read",  
> "feature\_uptime.read",  
> "feature\_observabilityCases.read",  
> "feature\_indexPatterns.read"  
> ],  
> "resources" : [  
> "space:dmv"  
> ]  
> }  
> ],  
> "run\_as" : ,  
> "metadata" : { },  
> "transient\_metadata" : {  
> "enabled" : true  
> }  
> }  
> }

---

<div class="post-metadata">

**Author:** ![Ryan\_Downey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ryan_downey/32/35987_2.png) [@Ryan\_Downey](https://discuss.elastic.co/u/Ryan_Downey)\
**Post date:** [September 18, 2023, 3:06pm UTC](https://discuss.elastic.co/t/kibana-space-unable-to-access-observability-functions/343275/2 "2023-09-18T15:06:13Z")

</div>

I figured it out. Observability doesn't automatically populate the specific indices delegated to it in the role. Within Observability you need to go to Observability --\> Logs --\> Settings in the upper right and update the index patterns/log indices for the data to be visible.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [October 16, 2023, 3:06pm UTC](https://discuss.elastic.co/t/kibana-space-unable-to-access-observability-functions/343275/3 "2023-10-16T15:06:35Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.