Removing doc permission inherited from parent : doc title continue to exist to non-granted users. (Not expected) · Issue #8290 · outline/outline · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create a ‘Projects’ collection with "No access" permission
Create a ‘Project A’ document
Give permission to the T1 group (e.g. Read only)
Create a ‘Hello A’ document in ‘Project A’
View the permissions for the ‘Hello A’ document.
Remove the ‘Has access through parent’ permission.
This is what the administrator sees for the ‘Projects’ collection.
As he has access to everything, he is obviously able to see the ‘Hello A’ document in the tree and its contents.
Following the removal of the permission inherited to ‘Project A’ for the document ‘Hello A’ as below:
This is what the test user sees for the ‘Projects’ collection.
We can see that he continues to see the ‘Hello A’ document in the tree structure even though he has lost access to it.
This is not logical. However, he can no longer consult its contents, as indicated by the ‘Not found’ message.
Expected Behavior
The test user no longer has access to the ‘Hello A’ document at all.
Logically, it should no longer be part of the tree structure for the test user:
Confidential information may be present in the name of a document ( i.e. a customer name, any ID, etc.).
Steps To Reproduce
No response
Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
This is not related to configuring Outline
Current Behavior
Use Case
This is what the administrator sees for the ‘Projects’ collection.

As he has access to everything, he is obviously able to see the ‘Hello A’ document in the tree and its contents.
Following the removal of the permission inherited to ‘Project A’ for the document ‘Hello A’ as below:

This is what the test user sees for the ‘Projects’ collection.

We can see that he continues to see the ‘Hello A’ document in the tree structure even though he has lost access to it.
This is not logical. However, he can no longer consult its contents, as indicated by the ‘Not found’ message.
Expected Behavior
The test user no longer has access to the ‘Hello A’ document at all.

Logically, it should no longer be part of the tree structure for the test user:
Confidential information may be present in the name of a document ( i.e. a customer name, any ID, etc.).
Steps To Reproduce
No response
Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: