WIP: Increase chapter admin permissions #169
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
@pjsier: Later today I'll send you a list of configuration menu items that Chapter Admins can have. Some, like Scopes, Territories and Chapters should not be given to Chapter Admins. |
Contributor
|
I updated #166 asking questions about whether this is still relevant |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Will close #166. Adds additional permissions to Chapter Admins and lets users with the superuser "Chapter Config" role add it to other users.
Doesn't cover the following permissions because they aren't scoped by chapter, but if it's alright for any chapter admin to edit them that can be modified here:
@OhMcGoo this is live on the staging site (https://arcdata-staging.herokuapp.com/), let me know if it's what you had in mind