Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Spike: Admin tool for managing roles and permissions #39

Closed
pamlo412 opened this issue Sep 8, 2020 · 4 comments · Fixed by #54
Closed

Spike: Admin tool for managing roles and permissions #39

pamlo412 opened this issue Sep 8, 2020 · 4 comments · Fixed by #54
Assignees
@jasalisbury
Labels
3 Story Points In epic 2 Issue is a child in the indicated parent epic spike V1.0 MVP Indicates the release version for the issue
Milestone
sprint1

Comments

@pamlo412
Copy link
Contributor

pamlo412 commented Sep 8, 2020 •
edited
Loading

User story: As a Smart Hub admin, I want a simple tool for managing roles and permissions so that I can ensure all TTA team members have the access they need.

Goals of this spike:

  • Investigate roles and permissions in HSES
  • Figure out a phase 1 way of managing them in Smart Hub. Note that the first admins will be Ryan and possibly Krys (as the only two team members with prod access). In a later phase, we may build a more user-friendly tool for use by OHS staff.
  • Document any critical architectural or implementation decisions
  • Communicate the plan to the product lead so she can create any needed followup stories in the backlog.
@pamlo412 pamlo412 changed the title Admin tool for managing roles and permissions Spike: Admin tool for managing roles and permissions Sep 9, 2020
@pamlo412 pamlo412 added the spike label Sep 9, 2020
@pamlo412 pamlo412 added this to the sprint0 milestone Sep 9, 2020
@pamlo412
Copy link
Contributor Author

pamlo412 commented Sep 9, 2020

Adding this story to sprint 0 for Josh to take a look at. It was intended for sprint 1 and may carry over into that sprint.

@pamlo412 pamlo412 removed this from the sprint0 milestone Sep 15, 2020
@pamlo412
Copy link
Contributor Author

Moving this story to sprint 1 for completion.

@pamlo412 pamlo412 added the 3 Story Points label Sep 15, 2020
@pamlo412 pamlo412 added this to the sprint1 milestone Sep 16, 2020
@jasalisbury jasalisbury mentioned this issue Sep 21, 2020
Merged
4 tasks
@jasalisbury
Copy link
Contributor

@pamlo412 The admin UI portion is mostly done, at least the UI part of it. There will be some more work to do on it once we nail down some more specifics on permissions. We will need tickets for the following:

  1. Implement Permissions on the backend. This includes the database schema and API endpoints. Will need to come to a consensus on how we want permissions to work. I would suggest separating each capability from the regions and having permissions be the combination of a region and capability. An example of a permission would be READ_REPORTS (the capability) on region 1. Some capabilities would be "regionless" (like the ADMIN capability). The admin UI as currently built assumes this is the path we will take but it could easily be changed.
  2. Update the UI to handle any new or updated permission/user schema (the first issue in this list). Also update the UI to actually fetch data from the API and call the API when saving/creating users.
  3. Determine which capabilities we need to define. Some possibilities:
  • ADMIN - Can edit users with the admin UI
  • SITE_ACCESS - Can view the TTAHUB site
  • READ_REPORTS - Can view activity reports for the region
  • READ_WRITE_REPORTS - Can view and update/create activity reports for the region

This was referenced Sep 21, 2020
Open
Open
@pamlo412
Copy link
Contributor Author

@jasalisbury I created #50, #51, and #52 for the follow-up spikes/stories for this spike. We'll review them at grooming tomorrow.

@rahearn rahearn mentioned this issue Sep 23, 2020
Closed
This was referenced Sep 24, 2020
Merged
Merged
rahearn pushed a commit that referenced this issue Sep 30, 2020
@jasalisbury
Fix deployed UI frontend issues (#39)
7b0a274 
* Fix deployed UI frontend issues

 * Serve the static frontend before applying the auth middleware
 * The CSP of the backend forces us to set INLINE_RUNTIME_CHUNK to
false. See https://create-react-app.dev/docs/advanced-configuration/

* Set sandbox branch to this branch

* Rename tests to match what they test
rahearn added a commit that referenced this issue Sep 30, 2020
@rahearn
Merge pull request #70 from adhocteam/main
a44a74d 
Fix deployed UI frontend issues (#39)
@pamlo412 pamlo412 added In epic 2 Issue is a child in the indicated parent epic V1.0 MVP Indicates the release version for the issue labels Oct 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jasalisbury jasalisbury

Labels
3 Story Points In epic 2 Issue is a child in the indicated parent epic spike V1.0 MVP Indicates the release version for the issue
Projects
None yet
Milestone
sprint1
Development

Successfully merging a pull request may close this issue.

Add Admin UI (#30) adhocteam/Head-Start-TTADP
2 participants
@jasalisbury @pamlo412