Profile: Adding dialog for seeing who has access - #2637
Merged
Conversation
Contributor
Author
|
selfie |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Who is this PR for?
internal team, district project leads
What problem does this PR fix?
When changes to permissions are made, there's no way for project leads to directly see who has access to an individual student. Down the line, this is something we'd want to make more visible all around as well, for more distributed review of permissions.
What does this PR do?
Adds a button for seeing this to the student profile, with minimal UI but a more student-centric perspective than other permissions tools. Access is controlled by a label, which will only be set for the internal team (making and reviewing permissions change now), and to project leads to help with that and to help debug any permissions-related issues going forward.
Screenshot (if adding a client-side feature)
Checklists
Which features or pages does this PR touch?
Does this PR use tests to help verify we can deploy these changes quickly and confidently?