Permissions and other missing features for 3rd-party-managed Home Assistant

After successfully installing and using HA in my own home for several years, I’d like to install Home Assistant in other houses as well. First for other members of the family. Then, maybe commercially in other houses in the area: there are many people that are not interested on tinkering and want a managed solution that simply works, and are willing to pay someone to do so.

However, at this moment there’s a major drawback: HA still doesn’t have a complete and secure permissions structure. If I’m managing, for example, my brother’s HA center, I don’t want allow him to upgrade it, or to modify certain core automations made by me.

This also would apply to vacation rental houses, where the house owner would want to have a hardened HA setup that is secure against smart guests with hacking capabilities.

I’m not sure if these features are currently a priority for Nabu Casa, but I think there will be many of us interested in having HA growing in that side.

Certainly I would be interested in contributing for this development. And probably I’m not the only one.

Thoughts?

Did you search for similar feature requests?
I bet there are a lot already and multiple will just spread the votes.

All the similar requests I have found are more focused in UI or Lovelace permissions.

But I honestly think that is only just one of the needed things. In order to achieve what’s needed, HA would really need users, temporary users and groups, and then totally granular ACL permissions for everything: you could have different user roles for the system manager, the house owner, the house guests…

I know there are plenty of those feature requests already.
New ones are being closed weekly it seems.

1 Like