I created a separate account for my children and assigned them their own Lovelace dashboard.
Recently I discovered that it’s also possible to set permissions per card. That made me wonder whether it would be better to duplicate an existing Lovelace dashboard and simply remove certain buttons (cards) instead.
However, I’m a bit confused about permissions:
Is it true that every user can still trigger all scripts (for example via iOS Shortcuts), including the children’s accounts?
I’d like to understand the best practice for restricting access properly.
Best practice is a good long talk with the kids about acceptable use and what you’re going to do if you catch them messing around with the system and hounding dev for RBAC…
You can add things like kiosk mode from HACS and hide endpoints. But remember at the end of the day. It’s open to all authenticated users. If someone knows the url and is authenticated they get there… Treat it that way.
I have now solved it this way for scripts that are not allowed to be started by another person; in that case, you need to add your own User-ID. This works when I start the script directly or via a button. If the script is started via an automation, you need to add None, because the automation does not provide a User-ID.
I only use the Telegram message for debugging. In that case, it’s better to display the message as <code>, so line breaks are rendered correctly.