# Global filter from specific Kibana instance

**URL:** <https://discuss.elastic.co/t/global-filter-from-specific-kibana-instance/205123>\
**Category:** Kibana\
**Created:** [October 24, 2019, 5:38pm UTC](https://discuss.elastic.co/t/global-filter-from-specific-kibana-instance/205123 "2019-10-24T17:38:09Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![nielsoncr](https://avatars.discourse-cdn.com/v4/letter/n/c57346/32.png) [@nielsoncr](https://discuss.elastic.co/u/nielsoncr)\
**Post date:** [October 24, 2019, 5:38pm UTC](https://discuss.elastic.co/t/global-filter-from-specific-kibana-instance/205123/1 "2019-10-24T17:38:09Z")

</div>

A customer with a particularly difficult performance problem regularly requests access to our performance logs stored in Elastic, viewed through Kibana. To assist this customer and not impact our internal Kibana instance we like to provide them their own Kibana instance, but restrict the data that can be seen on this Kibana instance. Is it possible to filter or restrict all queries coming from this customer's Kibana instance? Can a specific Kibana instance be configured to only show specific visualizations or spaces?

---

<div class="post-metadata">

**Author:** ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)\
**Post date:** [October 24, 2019, 8:33pm UTC](https://discuss.elastic.co/t/global-filter-from-specific-kibana-instance/205123/2 "2019-10-24T20:33:25Z")

</div>

@nielsoncr there are a few things we can use here.

With regard to Kibana Privileges you can create a role which only grants them access to a specific Space: [https://www.elastic.co/guide/en/kibana/current/kibana-role-management.html](https://www.elastic.co/guide/en/kibana/current/kibana-role-management.html) covers the options that we have here.

The user will also need Elasticsearch Privileges to be able to read the data for their visualizations. You can use [document level security](https://www.elastic.co/guide/en/elasticsearch/reference/7.4/document-level-security.html) and [field level security](https://www.elastic.co/guide/en/elasticsearch/reference/7.4/field-level-security.html) if granting a user read access to a specific index isn't granular enough.

---

<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:** [November 21, 2019, 8:33pm UTC](https://discuss.elastic.co/t/global-filter-from-specific-kibana-instance/205123/3 "2019-11-21T20:33:42Z")

</div>

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