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
{{ message }}
Repository navigation
Permission depends on the way of entering folders #12578
If users enter the subfolder directly out of their start-view, they can write to the subfolder, if they first open the top-folder and then the subfolder, they can't write to the folder
Expected behaviour
Allow the user to write even if they open the subfolder after the topfolder
Actual behaviour
see above
Server configuration
Operating system: Ubuntu 18.04
Web server: Nginx
Database: MySQL
PHP version: 7.2
Nextcloud version: 14.0.1
Updated from an older Nextcloud/ownCloud or fresh install: fresh
GitMate.io thinks possibly related issues are #7588 (Folder permissions), #8479 (Simplify sharing permissions for folders), #11717 (NotPermittedException: No create permission for folder), #8931 (external folder can not be shared with delete permissions), and #2268 (Users can delete shared folders without permissions).
I would suggest to not allow a file/folder which is inside an already shared folder to be shared to the same recipient a second time. But it would be usefull to let the owner "upgrade" the permission for a subfolder/file.
What do you think @nextcloud/sharing @nextcloud/designers ?
I think this is an impotent feature to upgrade the permissions in a shared fordert, to create finer permissions. It could be created like ACLs in filesystems. This were a more flexible system for permissions.
As discussed with @juliushaertl a possible way of doing this could be to check for a (new) share if there already exists a parent share to the same recipient and then only upgrading the permissions for this folder/file (inside the parent share) instead of creating a new share which shows up in the recipients root. What do you think @rullzer@schiessle? Would this be possible?
Is it necessary to rethink the way we do sharing? Wouldn’t it just be possible for Nextcloud to get "ah, now the person is in the subfolder, where they have write access to"?
Ideally nothing should change for people in the interface. This is a clear case of "it should just work as expected". :)
@jancborchardt yes, that's exactly the idea! The only thing to consider, I think, is if this shared subfolder should be visible in the recievers root directory (like a separate share) or not...?
Is it necessary to rethink the way we do sharing? Wouldn’t it just be possible for Nextcloud to get "ah, now the person is in the subfolder, where they have write access to"?
Yes, it would be possible, and yes it would be rethinking the way sharing works today 😉
But there are good chance that with Nextcloud 16 we will be able to solve it.
Reacted by Jonas Sulzer, John Molakvoæ, schlagi123 and shu0406
Activity
nextcloud-bot commentedon Nov 22, 2018
GitMate.io thinks possibly related issues are #7588 (Folder permissions), #8479 (Simplify sharing permissions for folders), #11717 (NotPermittedException: No create permission for folder), #8931 (external folder can not be shared with delete permissions), and #2268 (Users can delete shared folders without permissions).
violoncelloCH commentedon Nov 22, 2018
I would suggest to not allow a file/folder which is inside an already shared folder to be shared to the same recipient a second time. But it would be usefull to let the owner "upgrade" the permission for a subfolder/file.
What do you think @nextcloud/sharing @nextcloud/designers ?
schlagi123 commentedon Nov 24, 2018
I think this is an impotent feature to upgrade the permissions in a shared fordert, to create finer permissions. It could be created like ACLs in filesystems. This were a more flexible system for permissions.
violoncelloCH commentedon Nov 30, 2018
As discussed with @juliushaertl a possible way of doing this could be to check for a (new) share if there already exists a parent share to the same recipient and then only upgrading the permissions for this folder/file (inside the parent share) instead of creating a new share which shows up in the recipients root. What do you think @rullzer @schiessle? Would this be possible?
jancborchardt commentedon Dec 4, 2018
Is it necessary to rethink the way we do sharing? Wouldn’t it just be possible for Nextcloud to get "ah, now the person is in the subfolder, where they have write access to"?
Ideally nothing should change for people in the interface. This is a clear case of "it should just work as expected". :)
violoncelloCH commentedon Dec 4, 2018
@jancborchardt yes, that's exactly the idea! The only thing to consider, I think, is if this shared subfolder should be visible in the recievers root directory (like a separate share) or not...?
schiessle commentedon Dec 4, 2018
Yes, it would be possible, and yes it would be rethinking the way sharing works today 😉
But there are good chance that with Nextcloud 16 we will be able to solve it.
42 remaining items
shu0406 commentedon Jan 9, 2023
szaimen commentedon Jan 9, 2023
shu0406 commentedon Jan 9, 2023
shu0406 commentedon Mar 6, 2023