The second use of the word āspaceā in your last quote was a typo, apologies. Folders are relatively new so my brain defaulted to the word spaces. That should read as ā⦠but then they see nothing else within that folderā
In response to a space per department rather than a folder, that would fully depend on the complexity of the setup, no? If you have a situation where all of the databases for that department canāt be permissioned properly by entity permissions or a single space permission setup, then you may need to have multiple spaces so that all the relevant databases arenāt lumped into a single space permission setup. You definitely could still find workarounds for putting certain views under each of these relevant spaces, but I think my point is still valid.
Iād still love to see an example where an admin would want users to see a folder where that user canāt see any data. I can see why you would want a company intro folder for everyone to view basic wikis with a lot of documents or whiteboards, where the housed space permissions arenāt relevant. But in my mind that would happen less often than a mistaken visibility because a view was added to a folder. Maybe there is a setting on folders for āvisible for allā vs āvisible by spaces permissionsā.
I think my examples are adequate to understand the issue, but if itās not a priority for Fibery or isnāt a need from other users I understand. Just wanted to provide some feedback from my perspective.
Given that permissions can be controlled at the space, database or entity level, Iām not sure what access control you are looking to achieve that canāt be done whilst still having all databases for a department in a single space.
Maybe thereās a use case that isnāt covered by our current permissions model. Weād genuinely love to hear about it 
I agree
and thatās why folders are hidden from a user if they have no access to whatās inside them.
Yes. This is exactly the use case for items in the ādefault spaceā (= sidebar top level) - views/docs/whiteboards that youāre happy for everyone to see - whether in a folder or not.
Basically, default space does not have access control, so everyone sees everything inside.
If you want some people to see a view/doc/wb, and others not to, then it needs to live in a space (and that would seem to match the use case you have in mind, no?
)
Folders are great for creating groupings in the sidebar, but not for controlling who sees whatās inside them.
Folders do not support access control, only spaces, databases and entities do.
Folder contents inherit permissions from the space they are in, thus folder items in the ādefault spaceā inherit āvisible for allā and other folders inherit permissions from whatever space they are in.
I hope I am making sense 
To be clear, I promise Iām not trying to stubbornly refuse to agree with your perspective 
Iām just trying to fully understand what youāre hoping to do, and seeing if thereās something thatās currently missing from Fibery that prevents you from doing so 