-
Notifications
You must be signed in to change notification settings - Fork 85
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
Feature Request: Don't show sharing user's name to public #758
Labels
Comments
As far as I understand it, a public share via link is never related to any feature of the groupfolders app and always tied to the user who created the share. The groupfolders app is intended to share folders with groups and not with the public. What you are requesting is something like an "anonymous sharing" feature and this was already discussed here: nextcloud/server#9789. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We use the groupfolders to share files of our team to the public. But the public frontend shows the name of the user that cerated the share:
In our usecase, we don't want to expose that information to the public as it a) unnecessarily exposes the internal team structure and b) is confusing for the external receiver of that files as they don't know who that sharing person might be. Instead we need to have the group name as sender of a shared file (or no sender information at all). In fact, that is our primary reason to share files from a group folder instead of sharing them from a personal folder.
It would be perfect, if one could choose what information about the sender is shown to the receiver when a share is created. It also would be okay to show the groupfolder name as the sender or none at all. From my point of view the standard case for a groupfolder share is that it is not a personal share of one member.
This issue is inderectly connected to #117 to which I also agree: For our team internally the information about who shared files from our groupfolder is very interesting.
The text was updated successfully, but these errors were encountered: