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.

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

User Permissions #39

Closed
Zrrrpy opened this issue Apr 4, 2020 · 0 comments
Closed

User Permissions #39

Zrrrpy opened this issue Apr 4, 2020 · 0 comments
Labels
🙅‍♂️ User Permissions Work relating to different user permissions

Comments

@Zrrrpy
Copy link
Collaborator

Zrrrpy commented Apr 4, 2020

CASA Volunteer Portal - User Permissions

Permissions by roles (in order of least permissions)

Permission all roles have

  • View their own profile
  • Edit their own profile

Volunteer

  • Create new case_contact for their casa_case
  • Edit case_contact details for their casa_case (needs confirmation and details from stakeholders)
  • Edit teen_program_eligible for their casa_case
  • View case_contact details for all case_contacts they have had with active casa_case. They should not be able to see or edit case_contacts for casa_case that was reassigned to a different volunteer even if they might have created those case_contact records.

Supervisor

🚨 This role exists but the flows associated with this role do not as they are POST MVP 🚨

  • volunteers assigned to them, regardless of case assignment status (view and edit)
  • case_contacts associated with a supervisor's volunteer assignments (view and edit)
  • casa_cases associated with a supervisor's volunteer assignments (view and edit)
  • volunteer and case assignments for their volunteers (view and edit)
  • generate reports (need more details)

Admin

  • generate reports (need more details)
  • create new volunteers
  • assign supervisors to volunteers
  • assign a volunteer to a casa_case
  • unassign a volunteer from a casa_case
  • should be able to see all data but we might tailor the data shown to the dashboard just for usability purposes
  • admin should not be able to create case_contacts and any related objects we might build tied to case_contacts
@Zrrrpy Zrrrpy created this issue from a note in CASA Volunteer Portal (Epics - high level views of parallel issue tracks) Apr 4, 2020
@Zrrrpy Zrrrpy added the 🙅‍♂️ User Permissions Work relating to different user permissions label Apr 4, 2020
@Zrrrpy Zrrrpy removed this from Epics - high level views of parallel issue tracks in CASA Volunteer Portal Aug 15, 2020
@Zrrrpy Zrrrpy closed this as completed Aug 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🙅‍♂️ User Permissions Work relating to different user permissions
Projects
None yet
Development

No branches or pull requests

1 participant