# Watcher name and watcher indices name

**URL:** <https://discuss.elastic.co/t/watcher-name-and-watcher-indices-name/149940>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-alerting\
**Created:** [September 26, 2018, 7:06am UTC](https://discuss.elastic.co/t/watcher-name-and-watcher-indices-name/149940 "2018-09-26T07:06:55Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![laurent\_telle](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/laurent_telle/32/29612_2.png) [@laurent\_telle](https://discuss.elastic.co/u/laurent_telle)\
**Post date:** [September 26, 2018, 7:06am UTC](https://discuss.elastic.co/t/watcher-name-and-watcher-indices-name/149940/1 "2018-09-26T07:06:56Z")

</div>

Hi,

Is it possible to create watchers in a specific watcher name and give access to user only to this watcher indices then only to some specific watcher. watcher user and wtcher admin are too large !

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [September 26, 2018, 7:36am UTC](https://discuss.elastic.co/t/watcher-name-and-watcher-indices-name/149940/2 "2018-09-26T07:36:33Z")

</div>

Hey Laurent,

even though you could have a `.watches` index, configure privileges on those and insert watches into that index, I'd **highly** recommend **against** doing that, as you would loose additional checks that control if the watch has the correct structure that are only done in the Put Watch API. What you also cannot have is a watch index per user or group.

I do not think, that there is good solution to your problem right now, as the current security model only differentiates between watcher user/admin but not on a per watch basis.

--Alex

---

<div class="post-metadata">

**Author:** ![laurent\_telle](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/laurent_telle/32/29612_2.png) [@laurent\_telle](https://discuss.elastic.co/u/laurent_telle)\
**Post date:** [September 26, 2018, 7:49am UTC](https://discuss.elastic.co/t/watcher-name-and-watcher-indices-name/149940/3 "2018-09-26T07:49:31Z")

</div>

there is a big gap there, i'm working in a bank and having all user who can see watcher of others is forbidden, we use sms gateway, mattermost also. there is something to do quickly on this users are complaining cause i refuse access to them bacause of that.

can u raise it somewhere ?

---

<div class="post-metadata">

**Author:** ![laurent\_telle](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/laurent_telle/32/29612_2.png) [@laurent\_telle](https://discuss.elastic.co/u/laurent_telle)\
**Post date:** [September 26, 2018, 7:50am UTC](https://discuss.elastic.co/t/watcher-name-and-watcher-indices-name/149940/4 "2018-09-26T07:50:39Z")

</div>

goal is to offer complete alerting system, but in a good security context

---

<div class="post-metadata">

**Author:** ![willemdh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/willemdh/32/16922_2.png) [@willemdh](https://discuss.elastic.co/u/willemdh)\
**Post date:** [October 11, 2018, 5:10pm UTC](https://discuss.elastic.co/t/watcher-name-and-watcher-indices-name/149940/5 "2018-10-11T17:10:18Z")

</div>

We have the same requirement fyi. Watches should really be multitenant somehow. Just like reporting..

---

<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 8, 2018, 5:18pm UTC](https://discuss.elastic.co/t/watcher-name-and-watcher-indices-name/149940/6 "2018-11-08T17:18:38Z")

</div>

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