# Kibana Dashboard Templating

**URL:** https://discuss.elastic.co/t/kibana-dashboard-templating/127656
**Category:** Kibana
**Created:** [April 11, 2018, 2:38pm UTC](https://discuss.elastic.co/t/kibana-dashboard-templating/127656 "2018-04-11T14:38:44Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![alpa](https://avatars.discourse-cdn.com/v4/letter/a/8797f3/32.png) [@alpa](https://discuss.elastic.co/u/alpa)
#### Post date: [April 11, 2018, 2:38pm UTC](https://discuss.elastic.co/t/kibana-dashboard-templating/127656/1 "2018-04-11T14:38:44Z")

</div>

Hi,

I set up a custom Dashboard to monitor various aspects of a specific application. This application is deployed for multple clients and I give clients access to their own dashboard to monitor their own instances of the application.  
The way I've done this so far is using separate index patterns in Elasticsearch for each client and re-creating the same visualizations, searches and dashboard by exporting them from Kibana, doing a search and replace of the client name and importing them back into kibana.  
This is a bit tedious and error prone so I was wondering if there is a way to either automate the process or, even better, have some sort of shared "template" dashboard working for all clients, on their own indexes.

Thanks,  
Alessandro

---

<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: [April 11, 2018, 6:26pm UTC](https://discuss.elastic.co/t/kibana-dashboard-templating/127656/2 "2018-04-11T18:26:58Z")

</div>

Hey @alpa this is a really common ask, [https://github.com/elastic/kibana/issues/16917](https://github.com/elastic/kibana/issues/16917) is tracking this issue at the moment as we actively explore the solution. If you would give this issue a +1 or comment with your specific needs, it'll help us prioritize this issue appropriately.

---

<div class="post-metadata">

### Author: ![alpa](https://avatars.discourse-cdn.com/v4/letter/a/8797f3/32.png) [@alpa](https://discuss.elastic.co/u/alpa)
#### Post date: [April 13, 2018, 1:59pm UTC](https://discuss.elastic.co/t/kibana-dashboard-templating/127656/3 "2018-04-13T13:59:00Z")

</div>

Thank you Brandon

---

<div class="post-metadata">

### Author: ![rcowart](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rcowart/32/88091_2.png) [@rcowart](https://discuss.elastic.co/u/rcowart)
#### Post date: [April 13, 2018, 2:08pm UTC](https://discuss.elastic.co/t/kibana-dashboard-templating/127656/4 "2018-04-13T14:08:23Z")

</div>

You can actually do this pretty easy if you use appropriately named customer specific indexes, and X-Pack Security.

---

<div class="post-metadata">

### Author: ![alpa](https://avatars.discourse-cdn.com/v4/letter/a/8797f3/32.png) [@alpa](https://discuss.elastic.co/u/alpa)
#### Post date: [April 16, 2018, 8:35am UTC](https://discuss.elastic.co/t/kibana-dashboard-templating/127656/5 "2018-04-16T08:35:41Z")

</div>

I see what you mean. Currently we are not using X-Pack Security but I will keep it in mind

Thanks

---

<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: [May 14, 2018, 8:36am UTC](https://discuss.elastic.co/t/kibana-dashboard-templating/127656/6 "2018-05-14T08:36:08Z")

</div>

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