storyblok / storyblok

Info about Storyblok
https://storyblok.atlassian.net/servicedesk
322 stars 32 forks source link

Hiding Unauthorized Folders/Content Doesn't Hide Them, It Shows 'N/A' #771

Open hecktarzuli opened 2 years ago

hecktarzuli commented 2 years ago

The issue occurs while working with: (check one with "x")

Current behavior: When you assign a role to a user and tell it to 'hide folders if unauthorized', the user will see 'N/A' for the folder instead of actually hiding it.

Expected behavior: I expect the folder to actually be hidden. Showing a bunch of folders with 'N/A' is useless and confusing to users.

Steps to reproduce: Create 2 folders in 1 space. Create a role that has access to 1 of those folders Assign that role to a user, have that user log in and look at the Content folder. Notice they actually see 2 entries, and 1 shows 'N/A'

image V1 image V2 image

hecktarzuli commented 2 years ago

Likewise, results like this make for a horrible user experience.

image

appdcs commented 2 years ago

Hi all, we like using Storyblok but this issue prevents us from rolling it out to a wider group in our organization.

If a user is unauthorized and their role has the setting to hide unauthorized folders and content from them, then they should not see that content and folders at all.

Look at these examples and see how bad the user experience is, and how useless the "N/A" items are:

storyblok-771-issue1

storyblok-771-issue2

Please filter out the content item and folders for users who don't have permissions to see them.

nintra commented 8 months ago

Any news here? 2 years passed. This is horrible for any kind of users. Please add an option to hide all unrestricted folders.

similar to: https://github.com/storyblok/storyblok/issues/560 https://github.com/storyblok/storyblok/issues/272 https://github.com/storyblok/storyblok/issues/243

ZnaaMiR commented 5 months ago

I'm also interested in some progress here? It's quite annoying for our editors to just see a long list of content items they cannot access and they then still have to search for the content they actually have access to. Especially if it's only one story or folder they are responsible for. I understand you cannot remove the pages, but perhaps just hide them in the frontend? This is a recurring annoyance for our editors. It would contribute to a better user experience for sure (I know there's a favorite button, but no one are aware of it)

jonas-fortytwo commented 2 months ago

Is there any movement on this? The user experience is terrible. it's been 2.5 years.