# Does Kibana reporting support multitenancy?

**URL:** <https://discuss.elastic.co/t/does-kibana-reporting-support-multitenancy/63551>\
**Category:** Kibana\
**Created:** [October 20, 2016, 10:54pm UTC](https://discuss.elastic.co/t/does-kibana-reporting-support-multitenancy/63551 "2016-10-20T22:54:48Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![lekshmi](https://avatars.discourse-cdn.com/v4/letter/l/9e8a1a/32.png) [@lekshmi](https://discuss.elastic.co/u/lekshmi)\
**Post date:** [October 20, 2016, 10:54pm UTC](https://discuss.elastic.co/t/does-kibana-reporting-support-multitenancy/63551/1 "2016-10-20T22:54:48Z")

</div>

Does Kibana reporting plugin support Multitenancy?

Kibana kind of supports it, we were able to get around it with Shield, different ES indices per tenant and multiple instances of kibana.

Now the question is does the reporting plugin supports it ? Can we take a similar approach ?

---

<div class="post-metadata">

**Author:** ![Bargs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bargs/32/5429_2.png) [@Bargs](https://discuss.elastic.co/u/Bargs)\
**Post date:** [October 21, 2016, 4:59pm UTC](https://discuss.elastic.co/t/does-kibana-reporting-support-multitenancy/63551/2 "2016-10-21T16:59:50Z")

</div>

At the moment the index used by reporting is not configurable, so the multi-tenancy strategy you're using for Kibana won't work for reporting. However, we consider this a bug and in future releases you'll be able to configure reporting's index, giving each Kibana instance it's own reporting index and locking them down per tenant with Security.

---

<div class="post-metadata">

**Author:** ![jhn134910](https://avatars.discourse-cdn.com/v4/letter/j/90ced4/32.png) [@jhn134910](https://discuss.elastic.co/u/jhn134910)\
**Post date:** [April 10, 2017, 11:41am UTC](https://discuss.elastic.co/t/does-kibana-reporting-support-multitenancy/63551/3 "2017-04-10T11:41:31Z")

</div>

Do you know in what x-pack release it is planned for reporting to expose a configurable index?

Perhaps this may depend on any multi-tenancy features getting pushed into Kibana itself. The current state of play necessitating different kibana instances per tenant could be improved upon and there are a couple of alternative solutions being offered with search-guard and [https://github.com/wtakase/kibana-own-home](https://github.com/wtakase/kibana-own-home) plugins (i.e. a multi-tenancy solution with a single kibana instance). However, they don't offer any solution by way of reporting.

This stack is really neat, but issues around multi-tenancy are currently an obstacle to adoption. Are there any other options regarding reporting and multi-tenancy other than waiting for it, which may not be a problem if a solution is due to be delivered shortly.

---

<div class="post-metadata">

**Author:** ![Bargs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bargs/32/5429_2.png) [@Bargs](https://discuss.elastic.co/u/Bargs)\
**Post date:** [April 18, 2017, 4:45pm UTC](https://discuss.elastic.co/t/does-kibana-reporting-support-multitenancy/63551/4 "2017-04-18T16:45:20Z")

</div>

Configurable reporting index should come soon, it's already been worked on.

---

<div class="post-metadata">

**Author:** ![jhn134910](https://avatars.discourse-cdn.com/v4/letter/j/90ced4/32.png) [@jhn134910](https://discuss.elastic.co/u/jhn134910)\
**Post date:** [April 18, 2017, 5:44pm UTC](https://discuss.elastic.co/t/does-kibana-reporting-support-multitenancy/63551/5 "2017-04-18T17:44:51Z")

</div>

Thanks for the update Matt.

---

<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:** [July 6, 2017, 1:32pm UTC](https://discuss.elastic.co/t/does-kibana-reporting-support-multitenancy/63551/6 "2017-07-06T13:32:14Z")

</div>