Add Admin UI (#30) #54
Merged
Conversation
This file contains 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
* Add Admin UI The admin UI allows setting of user info and permissions. The user info is the user's name, email, job title and their region. Permissions are modeled to be flexible. A user permission is made up of a region and a scope. A scope represents the ability to do something specific, like READ_REPORTS. Combined with the region the permission system should be flexible enough to handle user's that need permissions that cross regions. Not yet done: * Any API work, including saving/modeling/REST endpoints * Checking/usage of permissions/user info in any other part of the TTAHUB * Add title to admin page * Change first/lastname field to full name * Set Harry's region to 1 This is to closer match the current permissions for the user * Add comment about region 0
jasalisbury
commented
Sep 24, 2020
Bumps [bl](https://github.com/rvagg/bl) from 4.0.2 to 4.0.3. - [Release notes](https://github.com/rvagg/bl/releases) - [Commits](rvagg/bl@v4.0.2...v4.0.3) Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Merged
3 tasks
|
This will be ready to merge once adhocteam#34 is merged in. |
* Region dropdown shows central office. Remove unnecessary key prop * Add missing semicolon * Use "co" as the central office region. 13 is already sometimes used
rahearn
approved these changes
Sep 24, 2020
rahearn
pushed a commit
that referenced
this pull request
Oct 27, 2020
Co-authored-by: Sarah-Jaine Szekeresh <[email protected]> Co-authored-by: kryswisnaskas <[email protected]>
rahearn
added a commit
that referenced
this pull request
Oct 27, 2020
CI: Use one image for dynamic security scan (#54)
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.
Description of change
The admin UI allows setting of user info and permissions. The user info is the user's name, email, job title and their region. Permissions are modeled to be flexible. A user permission is made up of a region and a scope. A scope represents the ability to do something specific, like
READ_REPORTS. Combined with the region the permission system should be flexible enough to handle user's that need permissions that cross regions.This is not the final version of the admin UI, although I feel like the UI itself won't be updated much. I expect the schema of the data that drives the admin UI will be updated and will require the UI to be updated as well. But I feel this is a good base for those changes to be applied when needed once the permission model has been finalized, and when we have a more definitive list of scopes.
Out of scope:
How to test
yarn deps(yarn docker:deps)yarn start:local(yarn docker:start)localhost:3000/adminIssue(s)
Checklist