# Tenant Kibana as BI

**URL:** <https://discuss.elastic.co/t/tenant-kibana-as-bi/372324>\
**Category:** Kibana\
**Created:** [December 23, 2024, 1:50pm UTC](https://discuss.elastic.co/t/tenant-kibana-as-bi/372324 "2024-12-23T13:50:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jodinathan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jodinathan/32/45821_2.png) [@jodinathan](https://discuss.elastic.co/u/jodinathan)\
**Post date:** [December 23, 2024, 1:50pm UTC](https://discuss.elastic.co/t/tenant-kibana-as-bi/372324/1 "2024-12-23T13:50:24Z")

</div>

We are considering using the ELK stack for a project that needs to provide BI capabilities to clients. To ensure security, we plan to implement RLS (Row-Level Security) and FLS (Field-Level Security), so clients only see their own data.

We would like to know if the following is possible:

- Create users with completely isolated environments. When a client accesses Kibana, they should have no awareness of other users, as if the environment were exclusively theirs.
- Clients should have **read-only** access to all available data.
- Prevent clients from creating reports, allowing them only to view the ones made available to them.
- Enable us (admins) to create reports and assign them to specific clients.
- Optionally, allow clients to access Kibana without needing a username and password, by providing access through our admin panel. This would involve generating a link that guarantees their entry directly.

---

<div class="post-metadata">

**Author:** ![GinkoLucas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ginkolucas/32/107055_2.png) [@GinkoLucas](https://discuss.elastic.co/u/GinkoLucas)\
**Post date:** [January 15, 2025, 4:40pm UTC](https://discuss.elastic.co/t/tenant-kibana-as-bi/372324/2 "2025-01-15T16:40:43Z")

</div>

Hello,  
In kibana you can :

- Create isolated environnements : [Spaces | Kibana Guide [8.17] | Elastic](https://www.elastic.co/guide/en/kibana/current/xpack-spaces.html)
- You can create Roles/User and affects them to a Space, so they can only see what's in their own space, and give them read-only access.
- Of course, admins can create dashboards and manage Spaces.
- And for Kibana access, it's possible to create access without authentication, but I don't recommend it for production use.