-
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
Grant circle admins more priviledges #217
Comments
mentioned in commit 90327a9df151a8346602648a03a53d81f6d3e934 |
mentioned in commit afe32d8809d8e291390cbf7494dbe8d0db14d6ed |
mentioned in commit ff23954d6db26ff7efe8f4289198a60cb1cceb56 |
mentioned in commit 24cab9c3be3038d4d95a426c8358e78b37c45141 |
mentioned in commit 00daf0e9f6d7d1a786627d26d4dcdbc379d7339d |
mentioned in commit b7e1bfb9a5767cd10d15b8a0a8bcd3e633d93d72 |
mentioned in commit f434851 |
mentioned in commit 95ea2c71643b50a3ba4f3726bc15d7bd07f94277 |
mentioned in commit 4b87a26f76e7d357b22faf92e3586bb3421d8671 |
mentioned in commit 508461de0cc1dfe13f47162b0d98151422ede0f4 |
mentioned in commit 2070eb5 |
Currently we only grant circle owners admin privileges:
Technically, only deleting the circle is limited to circle owners, so we at least should allow the last two to ordinary admins as well.
I'm not sure how to implement this best, though. Maybe instead of exposing a boolean
admin
flag for each collective, we should introduce alevel
field that exposes the circle member status (owner, admin, moderator, member). This would also be a good first step towards proper access level management.The text was updated successfully, but these errors were encountered: