Configurable for a few different use cases would be really nice. Toggle on a specific behavior, one for default per device, one for default per user, and ones for default by screen resolution and/or user agent.
1 Like
Would love to see default per device. This would make room specific UI much easier to implement.
2 Likes
While not exactly what you’re asking for, that’s sort of achievable now. When you login to HA that specific login session / device can have a default dashboard set. That’s what happens when you set a dashboard to the default in the user options, it’s saved for that particular device, not for all devices.
The specific request that this thread is about is for being able to administratively set a default dashboard for users so that any device they login to gets that as the default and if they want to change the default to something else for that device then they can with the current settings behavior.
Would be great to be able to assign what Dashboards regular users see and what not…
Maybe to add here…
Why the dashboard per user is needed, and not per device…: because when you are the house admin, you want to make live easy for your users. And prevent users to configure their dashboards per device. Or also have different people use the same user…
3 Likes
I want to be able to set a specific VIEW as default on one specific device (for one user also fine, same result in my use-case (kiosk tablet)). This is not possible at the moment unfortunately.
It because one user may want to login using different screens, phone, pc and tablet. Best way is to have a user for your tablet and set the default dash on the tablet. And only use the tablet login on the tablet. That is what I do.
So there are tons of arguments to both sides of this, so why can both options coexist? Have a setting for default dashboard per user account and if it’s not set then fallback to the per device default. Would be nice on the user page to list all the dashboards and just have checkboxes to allow or disallow viewing of said dashboard, seems a simple solution.
1 Like
But on the device you could login as an “user” or as an “admin”. What if the default View/Dashboard you choose is admin-only? What has to shown then for the “user” on this device?
Admin is not an option. It’s a normal user who’s default view should not be view 1 of a dashboard 1 but view 1 of dashboard 2. Currently impossible.
1 Like
This has nothing to do with admin or user. It has something to do with the combination of account and device (user or admin doesn’t matter; both are accounts).
At the end (as I think to know) in HA there is no real difference between “admin” and “user”. The API can be fully called by both. HA has no authentication system, only an authorization system. Just some links and Dashboards are hidden for “user”.
Nice to know. And indeed, HA lacks a “bit” of flexibility here. So still, it’s much talking without saying anything helpful unfortunately. …as it simply is not possible at the moment 
I think my biggest issue is that on the iOS app at least, if you have a different internal and external URL, it has two different login sessions (?) so you end up with different sidebars, themes, default dashboards etc depending on if you’re in or out of the house!
2 Likes
At least you can set the default theme. Here is the automation action:
service frontend set_theme
Yeah, well… a theme is not a dashboard is not a view, right. So… 
No idea what you’re even trying to say here
I was saying that
is the answer to a completely different question and not helpful in this topic at all.
It is helpful because if you use backend selected and set the theme, it does create a default theme for all users.
Oh dear… this is about a default dashboard right? A theme is a theme, a dashboard is a dashboard. Please explain.
Being able to define how a dashboard looks is not helpful when aiming at setting “a default dashboard per user”, isn’t it?
People come to threads all the time for information when they google things. 
.
Just because it’s not relevant to you doesn’t meant it’s not relevant for someone else.
And it’s still on topic because it’s about the frontend, so relax.