User story: Enable admin to assign permissions to Smart Hub users (AC-2)

[pamlo412]

This user story will tie the spike and backend work from #39, #50, and #51 together so that we have a fully functioning admin tool in which to set or update user permissions for the Smart Hub.

User story:
As a Smart Hub admin, I want to be able to specify the regions and read/write/admin access permissions of Smart Hub users so that the TTA team members can access what they need to complete their work in Smart Hub.

Acceptance criteria:

1. Launch the admin tool by clicking a link in Smart Hub that only admin users can see (implementation choice to be confirmed).
2. Search for and select a user for whom to set permissions.
3. Set permissions for key permutations as defined in Spike: Define permissions  #51 :
   • user A can access region x and has read/write permissions
   • user B can access region y and has read only permissions
   • etcetera - fill in the rest of these permutations once Spike: Define permissions  #51 is done
4. Remove fake scope permissions: third_scope, fourth_scope
5. Remove cities from region name; the number suffice.
6. Change Job Title label to read "Role".
7. Add additional titles to the Role list. The full list should include the following:
   • Regional Program Manager
   • COR
   • Supervisory Program Specialist
   • Program Specialist
   • Grants Specialist
   • Central Office
   • TTAC
   • Admin. Assistant
   • Early Childhood Manager
   • Early Childhood Specialist
   • Family Engagement Specialist
   • Grantee Specialist Manager
   • Grantee Specialist
   • Health Specialist
   • System Specialist
8. Remove Site_Access option from Global Permissions
9. Change name of permissions from Read and Read_write "Reports" to Read and and Read_write "ActivityReports."
10. Ensure the following fields are required before you can save a new user:
    • Email
    • Full name
    • Region
    • Role

Dependency:

• login needs to be functional for this story to be completed

Exclusions:

• creation of users who don't yet exist in HSES - no story needed, HSES will handle this need
• login - see Enable users to log into and out of TTA Smart Hub (IA-2) #4
• creation or import of the first set of Smart Hub users

[pamlo412]

Agreed at grooming: we'll push this story back to the Backlog column for now. When #51 gets done, we will fill in the permission permutations and regroom this story.

[pamlo412]

Revised job title requirements to change label and add list of roles provided by @PatricePascual-ACF. And here is the source document for this list.