Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documents on thrash are visible by everyone #6808

Closed
WilliamSoler opened this issue Apr 15, 2024 · 2 comments
Closed

Documents on thrash are visible by everyone #6808

WilliamSoler opened this issue Apr 15, 2024 · 2 comments
Labels
bug more information needed This issue will be automatically closed unless more details are provided self-hosted Issues related to self-hosting the code

Comments

@WilliamSoler
Copy link

A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

  1. Delete a file from a collection whose permissions only allow accessibility by a user or group.
  2. A user who could access the mentioned file before, can now see it in the thrash files

Expected behavior
A clear and concise description of what you expected to happen.

Outline (please complete the following information):

  • Install: self-hosted
  • Version: v0.75.2
Copy link

linear bot commented Apr 15, 2024

@potatoone
Copy link
Contributor

I have tested it on the latest community edition and there is no problem.
Subdocuments that are deleted from a collection with no access will not be seen in the recycle bin by users without permission.
Unless you re-grant collection access to another person or group, excluding Viewer, after deleting the subdocument.
😉

@tommoor tommoor added more information needed This issue will be automatically closed unless more details are provided self-hosted Issues related to self-hosting the code labels Apr 15, 2024
@tommoor tommoor closed this as completed Apr 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug more information needed This issue will be automatically closed unless more details are provided self-hosted Issues related to self-hosting the code
Projects
None yet
Development

No branches or pull requests

3 participants