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

Move permission for shared files/subfolders #44404

Closed
enjeck opened this issue Mar 22, 2024 · 3 comments · Fixed by #45652
Closed

Move permission for shared files/subfolders #44404

enjeck opened this issue Mar 22, 2024 · 3 comments · Fixed by #45652
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap design Design, UI, UX, etc. enhancement feature: sharing
Milestone

Comments

@enjeck
Copy link

enjeck commented Mar 22, 2024

When sharing files/folders publicly, I have the option to specify permissions like "edit", "copy", "delete". It would be nice if there was an additional "move" permission for moving files between subfolders.

How to use GitHub

  • Please use the 👍 reaction to show that you are interested into the same feature.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.
When sharing files/folders publicly, I have the option to specify permissions like "edit", "copy", "delete". It would be nice if there was an additional "move" permission for moving files between subfolders. When I share files/folders with the "edit", "create" and "read" permissions, but without the "delete" permission, users are unable to move files. Even though they can't move things, the "Move or copy" button still shows, which is confusing.
Screenshot from 2024-03-22 11-34-42

Describe the solution you'd like
Either there's a special "move" permission. Or the "Move or copy" option is removed (or modified) since the user can't perform that action.

Describe alternatives you've considered

Additional context

@enjeck enjeck added enhancement design Design, UI, UX, etc. 0. Needs triage Pending check for reproducibility or if it fits our roadmap ux labels Mar 22, 2024
@jancborchardt jancborchardt removed the ux label Apr 2, 2024
@godfuture
Copy link

I think splitting "delete" permission into "move" and "delete" is more important than adjusting UI to specific permissions in the folder. It totally makes sense to differ between move and delete, because when allowing to move files the sharing user can rest asured files will not disappear. Whilst giving delete permission allows them to change the amount of files available.

@krupper
Copy link

krupper commented May 21, 2024

In my opinion, the UI should not display any options that are not available. In this case, "move or copy". In our organization, we increasingly have questions as to why folders in shares (without delete permission) cannot be moved. The corresponding error message for the recipient of a share is also not meaningful.

@airbenich
Copy link

Same here +1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap design Design, UI, UX, etc. enhancement feature: sharing
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants