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
When a user that does not have all permissions reshares a file/folder shared to him, the owner can't add any permissions to the third user that the second user does not have (by design). Though it looks in the UI as if it is possible to add those permissions it is not greyed out. Only when you try to safe it shows an error.
Edit can be selected for share to User3
Error is displayed when updating the share
Steps to reproduce
User1 shares to User2 without edit permission
User2 shares to User3 without edit permission
User1 sees share to User3 and it seems as if User1 could add permissions to the share that User 2 does not have.
Expected behavior
User1 sees Edit permission greyed out, or is able to give User3 edit permission.
Side note
The re-share functionality also has some other weird edge cases still. e.g. in the scenario above. If User2 gets a permission removed the user who received a reshare keeps the permission.
Nextcloud Server version
master
The text was updated successfully, but these errors were encountered:
Bug description
When a user that does not have all permissions reshares a file/folder shared to him, the owner can't add any permissions to the third user that the second user does not have (by design). Though it looks in the UI as if it is possible to add those permissions it is not greyed out. Only when you try to safe it shows an error.
Edit can be selected for share to User3
Error is displayed when updating the share
Steps to reproduce
Expected behavior
User1 sees Edit permission greyed out, or is able to give User3 edit permission.
Side note
The re-share functionality also has some other weird edge cases still. e.g. in the scenario above. If User2 gets a permission removed the user who received a reshare keeps the permission.
Nextcloud Server version
master
The text was updated successfully, but these errors were encountered: