# Inquiry About RBAC and User Interface Separation in Homey Pro

**URL:** <https://community.homey.app/t/inquiry-about-rbac-and-user-interface-separation-in-homey-pro/129066>\
**Category:** Questions & Help\
**Tags:** app, homey-pro\
**Created:** [January 28, 2025, 7:39am UTC](https://community.homey.app/t/inquiry-about-rbac-and-user-interface-separation-in-homey-pro/129066 "2025-01-28T07:39:42Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tomas\_Krcmar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tomas_krcmar/32/120933_2.png) [@Tomas\_Krcmar](https://community.homey.app/u/Tomas_Krcmar)\
**Post date:** [January 28, 2025, 7:39am UTC](https://community.homey.app/t/inquiry-about-rbac-and-user-interface-separation-in-homey-pro/129066/1 "2025-01-28T07:39:43Z")

</div>

HI, I’m currently working on a project using Homey Pro, and I have a specific question regarding user management and role-based access control (RBAC).

Are there any plans to introduce RBAC functionality in Homey Pro? Specifically, I’m looking for a way to separate the end-user interface from the programming environment. Ideally, I’d like to provide users access only to control devices (e.g., turn lights on/off, adjust intensities, view sensor data) without exposing flows or system-level configurations.

Additionally, is there any official or recommended solution (such as an external dashboard or app) to achieve this separation in the current Homey Pro ecosystem?

Thanks!

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [January 28, 2025, 11:22am UTC](https://community.homey.app/t/inquiry-about-rbac-and-user-interface-separation-in-homey-pro/129066/2 "2025-01-28T11:22:07Z")

</div>

This is requested pretty often since I use Homey (Q3 2020), but it doesn’t seem to be on the (priority) list.

---

<div class="post-metadata">

**Author:** ![Dijker](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@Dijker](https://community.homey.app/u/Dijker)\
**Post date:** [January 28, 2025, 11:48am UTC](https://community.homey.app/t/inquiry-about-rbac-and-user-interface-separation-in-homey-pro/129066/3 "2025-01-28T11:48:02Z")

</div>

> [@Tomas\_Krcmar](#):
>
> I’d like to provide users access only to control devices (e.g., turn lights on/off, adjust intensities, view sensor data) without exposing flows or system-level configurations.

Afaik that is the Gues role in Homey.

> **[Adding, managing & removing user accounts on Homey](https://support.homey.app/hc/en-us/articles/360012615814-Adding-managing-removing-user-accounts-on-Homey)**
>
> With Homey, you can create accounts for all your smart home users. This is great because you don’t have to share your account or password. It also allows you to manage and control who has access.
> N...

But that also enables them to start flows now.

Create a dashboard with only the devices and lock their dashboard.

That should be the announced (upcoming) solution by Athom