Skip to content
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

Closed
mejo- opened this issue Jul 11, 2021 · 10 comments
Closed

Limit who can edit Collectives (ACLs) #191

mejo- opened this issue Jul 11, 2021 · 10 comments

Comments

@mejo-
Copy link
Member

mejo- commented Jul 11, 2021

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.

@mejo-
Copy link
Member Author

mejo- commented Jul 13, 2021

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.

@mejo-
Copy link
Member Author

mejo- commented Jul 28, 2021

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.
This content should not be editable for all users.

Thanx for Your great work

@mejo-
Copy link
Member Author

mejo- commented Oct 20, 2021

marked #250 as a duplicate of this issue

@mejo-
Copy link
Member Author

mejo- commented Oct 20, 2021

marked this issue as related to #250

@mejo-
Copy link
Member Author

mejo- commented Jan 24, 2022

mentioned in commit 9d376390747a62b5c83055ce9e62d6ca4e98adf9

@mejo-
Copy link
Member Author

mejo- commented Jan 26, 2022

mentioned in commit a9c754eaed403ca9c9088eb24cc293fe1ca352a1

@mejo-
Copy link
Member Author

mejo- commented Jan 27, 2022

mentioned in commit 034907ad76d8e29d0dc326759751eb854fc9a9ea

@mejo-
Copy link
Member Author

mejo- commented Feb 9, 2022

mentioned in commit 4c1d308792b12184a4338f4882bd9aa58acde88c

@mejo-
Copy link
Member Author

mejo- commented Feb 10, 2022

mentioned in commit c5142a76a61d4c190fe40ddd0b898dd98bede830

@mejo-
Copy link
Member Author

mejo- commented Feb 10, 2022

mentioned in commit 1bec187

@mejo- mejo- closed this as completed Dec 13, 2022
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

1 participant