Implimination of a user base login exploiting Custimize

Feature Requests
1

Using conditions we can hide sensors from the front end using the following syntax:

customize:
    sensor.living_room_motion:
      hidden: true

By default we can see any sensor that does not have the hidden: true option. What if HASS obtained a user name at login. And with that user name HASS then used that variable to expand the hidden option. The expanded syntax would be to put a username in the hidden option to therefor hide that sensor from that user.

customize:
    sensor.living_room_motion:
      hidden: username, username2

This could be then expanded to group view option and panel_iframes with a new hidden option. And then a new option to hide the Developer Tools for users.

This may not be the simplest feature to implement but would be well worth the time for the user base. I see many situations where a household would want to be able to limit use of the interface for certain users. This would allow parents to give children access to the interface without giving them keys to the kingdom. Or even guest. Say you give your teenage children access as HASS is now. Halloween is coming up. Good way to play some haunted house pranks on siblings. Or maybe you have wireless locks and you want to be able to let your house keeper unlock the door without giving them a key or them having to install software on there phone. This way you just give them the URL and user info and the only option they get is a switch to unlock the door. That switch could even trigger automation to turn off the alarm and let you know they are there.

2