# Different user types

**URL:** <https://discuss.elastic.co/t/different-user-types/175701>\
**Category:** Kibana\
**Tags:** elastic-stack-security\
**Created:** [April 7, 2019, 5:57am UTC](https://discuss.elastic.co/t/different-user-types/175701 "2019-04-07T05:57:09Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [April 8, 2019, 5:54pm UTC](https://discuss.elastic.co/t/different-user-types/175701/2 "2019-04-08T17:54:04Z")

</div>

Hi, please take a look at Dashboard-only mode: [https://www.elastic.co/blog/kibana-dashboard-only-mode](https://www.elastic.co/blog/kibana-dashboard-only-mode)

With this, an admin user will be able to set up all the dashboards, and enable logged-in users to only see them; but not make any changes that persist in the .kibana index.

If you don't want users to have to log in first, you could look into establishing a special link for the users that has traffic first go through a reverse proxy that decorates the request with authentication headers, automatically logging in the visitors as dashboard-only visitors. See: [Auto-authenticating to iframe-embedded Kibana dashboard](https://discuss.elastic.co/t/auto-authenticating-to-iframe-embedded-kibana-dashboard/46091/3)

Please be aware that even in dashboard-only mode, the users still could use Kibana to create expensive queries to Elasticsearch, so use caution if you are planning on hosting Kibana publicly to the Internet.

---

_[View the full topic](https://discuss.elastic.co/t/different-user-types/175701)._