Kill the `denial` feature
We have the experimental feature to deny access to a folder, even when a parent folder is shared with read or write access with the same person.
Can we kill that feature? It always has been in an experimental state and I don't see us improving it. Do we still need it for whatever reason?
I can only reiterate, that organization that have many clients, supporting them always the same way, like
tax advisors Media agencies Print consulting companies
do have the requirement of the above feature.
Maybe the sub-space concept could address this requirement too, Otherwise we should not drop!
I can only reiterate, that organization that have many clients, supporting them always the same way, like
tax advisors Media agencies Print consulting companies
do have the requirement of the above feature.
Maybe the sub-space concept could address this requirement too, Otherwise we should not drop!
The usability for creating and maintaining denials on individual folders is from hell. From everything I've heard this is most important (maybe even "only") on the space root level, thus something in the area of sub-spaces, space categorization, space tagging, etc would be both easier to maintain and easier to understand (both from an end user perspective).
Especially easier to understand. Denials look good on the feature list, but in practise using them quickly leads to a situation where nobody understands any more why something is shared to somebody, or not. That is - from a perspective that we want to provide transparent security - not ideal.
@MaSCH-25 now, a few month later, has your position changed on this?