Ability to manage access to Panels #11242
Replies: 8 comments
-
Configure UI menu button should already be covered by the permissions system. Regular users will not be able to edit the user interface, clicking that button will just show a help menu. That will also hide other things like the Configuration panel and Developer Tools from the sidebar. So make sure that your children accounts are set to "User" and not "Administrator" .. Newly created accounts are created as admins by default unless you manually go in and change it afterwards. I have an issue about that here #3604. Logbook and History will still appear in the sidebar though, yeah. I do kind of agree those should be hidden, and probably even the Map too. |
Beta Was this translation helpful? Give feedback.
-
Well, what is needed is a proper ACL system. |
Beta Was this translation helpful? Give feedback.
-
You can hide tabs from users in core, no need for custom header. An ACL system is in the works for some time, but a lot of work to implement. You are more than welcome to help. |
Beta Was this translation helpful? Give feedback.
-
I known ACL is a lot of work, especially when it's an afterthought. |
Beta Was this translation helpful? Give feedback.
-
@fribse try https://github.com/iantrich/restriction-card |
Beta Was this translation helpful? Give feedback.
-
Hi, I too would like to limit some sidebar items view from the kids but although not what I want, here's something I found that can hide/rearrange some items from the side bar: |
Beta Was this translation helpful? Give feedback.
-
@bramkragten It would be really important for us, how can we jump in and help ? What is the Issue, branch, user story related ? |
Beta Was this translation helpful? Give feedback.
-
It would also be nice to add specific items (like grafana) to specific non admin users. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
The request
As we use the HA more and more also as a GUI for the smarthome, and not just an automation tool, it really needs to have better user seperation and control.
It's nice that you can limit certain pages from being shown to certain people, but the 'logs' and 'history', edit frontpage menu and other standard pages also needs to be excempted for certain users by choice.
Then there is nice to haves:
Disable card-types for specific users (ie. all camera cards, or switch cards)
The alternatives
I've tried limiting access to the top menu with Custom Header but that is then for all users, not just for the one currently logged in.
With the new 0.107 I can create multiple frontends, but despite that it is very nice, that just doubles/tripple/quadrupels the work for setting up the UI.
Additional information
Beta Was this translation helpful? Give feedback.
All reactions