visible: option on view does not hide for non set users

[Mariusthvdb]

Checklist

• [X] I have updated to the latest available Home Assistant version.
• [X] I have cleared the cache of my browser.
• [X] I have tried a different browser to see if it is related to my browser.

Describe the issue you are experiencing

using the visible option on a view does not hide the view from non listed users. Any page used in a dashboard with a specific user set for visible is displayed for all users.

Describe the behavior you expected

only show the view to a listed user

Steps to reproduce the issue

1. make a view with the visible: option

...

What version of Home Assistant Core has the issue?

2021.11dev20211022

What was the last working version of Home Assistant Core?

dk

In which browser are you experiencing the issue with?

Safari, Chrome, FF

Which operating system are you using to run this browser?

Big sur 11.6

State of relevant entities

No response

Problem-relevant frontend configuration

title: Settings motion
path: settings_motion
visible: 3a8redacted356b63
icon: mdi:run-fast
cards:

title: Light settings
path: light_settings
icon: mdi:home-lightbulb
visible:
  - user: 3a8redacted356b63
cards:

Javascript errors shown in your browser console/inspector

none

Additional information

nothing much really, other than a discussion I started earlier for allowing 'require_admin: true' also on views.

btw, I also tested the above configs with a secret (dont want the user_id in the frontend lovelace files)

title: Settings motion
path: settings_motion
visible: !secret admin
#background: radial-gradient(crimson, skyblue)
icon: mdi:run-fast
cards:

title: Light settings
path: light_settings
icon: mdi:home-lightbulb
visible:
  - user: !secret admin
cards:

with the secret setup in secrets.yaml as:

admin: 3a8redacted356b63

[Mariusthvdb]

Ive found this to be a two-fold issue:

• main issues with Kiosk-mode plugin, filed an issue in the repo https://github.com/maykar/kiosk-mode/issues/77
• Lovelace does have an issue, because it will only work with:

title: Settings motion
path: settings_motion
visible:
  - user: !secret admin

and not with the also listed option

visible: !secret admin

which is either a bug in Lovelace, or a documentation error?

[SkateWarp]

I had the same issue now, well not me, my dad's iPhone, with HA app. His user only have visibility to one tab, for whatever reason he could view and interact with other tab, which is configured to not to show for his user.

Closing the app, and opening it again "fixes" it until happens again. It's somewhat annoying, specially when you have non-techy parents. 😅

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Mariusthvdb]

keep

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Mariusthvdb]

Keep

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Mariusthvdb]

keep

[maslyankov]

I have faced an issue connected to this, I guess. When you hide a view for an user, if you know or guess the view url, you can still access it using the user it is hidden for.

[bevanm8]

This is still an issue, I have some tabs that I set to be only visible to me. Power sockets that I only use for power monitoring that I don't want switched off, additional information about things etc, that no one else needs or cares about. To my surprise all the tabs I have set up as visible to me only, are visible to everyone.

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[maslyankov]

Issue is still persistent.

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Mariusthvdb]

keep needs testing before closing

[bramkragten]

This is a documentation issue, visible should either be a boolean or a list of users.

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.