-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Limit who can edit Collectives (ACLs) #191
Comments
Hey @ya-d, Thanks for the feature request! That's certainly something we have on our roadmap, but probably it will take a bit until we find time to implement it. We probably have to implement proper permission management at one point. That would have to be done both in backend and frontend - as we'd have to limit (DAV) file access permissions as well. |
In GitLab by @mike0000 on Jul 28, 2021, 21:54 I would be happy to get this feature too :) The Idea is to use collectives ability to build a 'landing page' for the whole nextcloud. Thanx for Your great work |
marked #250 as a duplicate of this issue |
marked this issue as related to #250 |
mentioned in commit 9d376390747a62b5c83055ce9e62d6ca4e98adf9 |
mentioned in commit a9c754eaed403ca9c9088eb24cc293fe1ca352a1 |
mentioned in commit 034907ad76d8e29d0dc326759751eb854fc9a9ea |
mentioned in commit 4c1d308792b12184a4338f4882bd9aa58acde88c |
mentioned in commit c5142a76a61d4c190fe40ddd0b898dd98bede830 |
mentioned in commit 1bec187 |
In GitLab by @ya-d on Jul 11, 2021, 12:04
Nextcloud 22 allows differentiation between owners, admins, moderators and members within Circles. I know that Collectives are owned by the collective (or Circle that is 😄 ) but there are many situations where it is desirable to limit writing access to certain members.
It would be great to have a setting that limits editing of Collectives to owners, admins or moderators.
Thanks for considering.
The text was updated successfully, but these errors were encountered: