# Kibana 5.0 Alpha 3 Security Settings

**URL:** <https://discuss.elastic.co/t/kibana-5-0-alpha-3-security-settings/53748>\
**Category:** Kibana\
**Created:** [June 23, 2016, 8:32am UTC](https://discuss.elastic.co/t/kibana-5-0-alpha-3-security-settings/53748 "2016-06-23T08:32:55Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kennedy\_Kan1](https://avatars.discourse-cdn.com/v4/letter/k/cc9497/32.png) [@Kennedy\_Kan1](https://discuss.elastic.co/u/Kennedy_Kan1)\
**Post date:** [June 23, 2016, 8:32am UTC](https://discuss.elastic.co/t/kibana-5-0-alpha-3-security-settings/53748/1 "2016-06-23T08:32:55Z")

</div>

I have set up some roles and users in the security page.

 ![](https://us1.discourse-cdn.com/elastic/original/2X/d/df85bb0ffa238db9c1cd7d416f4c96bb0c413dc9.PNG)  
 ![](https://us1.discourse-cdn.com/elastic/original/2X/f/f625cb79fe4475562c707fcad0b19a28b0f1c123.PNG)

But it turns out that nothing can be seen when I logged in as Ray\_Wong

What is wrong with that?

---

<div class="post-metadata">

**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\
**Post date:** [June 24, 2016, 4:56pm UTC](https://discuss.elastic.co/t/kibana-5-0-alpha-3-security-settings/53748/2 "2016-06-24T16:56:27Z")

</div>

Hi Kennedy,

You'll need to create a `kibana_user` role and give the users that role so they can use Kibana. The role will need the `manage`, `read`, `index` permissions on the `.kibana*` indices. You can assign as many roles to your Kibana users as you need, so you can assign other roles that give permission over your data indices.

Note that this will be made easier in alpha4, which will provide a default `kibana_user` role for you.

---

<div class="post-metadata">

**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\
**Post date:** [June 24, 2016, 5:04pm UTC](https://discuss.elastic.co/t/kibana-5-0-alpha-3-security-settings/53748/3 "2016-06-24T17:04:25Z")

</div>

Couple more things:

- If you want your Kibana users to be able to create visualizations, they will also need the `write` permission on the `.kibana*` indices.
- The role just needs `read` and `view_index_metadata` permission on the indices in order to access them in Kibana. Looks like you have `read` and `manage`

---

<div class="post-metadata">

**Author:** ![Kennedy\_Kan1](https://avatars.discourse-cdn.com/v4/letter/k/cc9497/32.png) [@Kennedy\_Kan1](https://discuss.elastic.co/u/Kennedy_Kan1)\
**Post date:** [June 24, 2016, 5:15pm UTC](https://discuss.elastic.co/t/kibana-5-0-alpha-3-security-settings/53748/4 "2016-06-24T17:15:29Z")

</div>

Thank you  
That helps a lot. But one more point for me to concern is that, if I didnt grant rights for a user to create or delete an index, he can only be stopped from doing that in console page. But how can I also block the user from deleting or creating existing one in the indices page of settings.  
Also, if the user create a new index through logstash how am I able to detect the user who create it?

---

<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:49pm UTC](https://discuss.elastic.co/t/kibana-5-0-alpha-3-security-settings/53748/5 "2017-07-06T13:49:19Z")

</div>


