You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 activecasa_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
The text was updated successfully, but these errors were encountered:
CASA Volunteer Portal - User Permissions
Permissions by roles (in order of least permissions)
Permission all roles have
Volunteer
case_contact
for theircasa_case
case_contact
details for theircasa_case
(needs confirmation and details from stakeholders)teen_program_eligible
for theircasa_case
case_contact
details for allcase_contacts
they have had withactive
casa_case
. They should not be able to see or editcase_contacts
forcasa_case
that was reassigned to a different volunteer even if they might have created thosecase_contact
records.Supervisor
🚨 This role exists but the flows associated with this role do not as they are POST MVP 🚨
case_contacts
associated with a supervisor's volunteer assignments (view and edit)casa_cases
associated with a supervisor's volunteer assignments (view and edit)Admin
case_contacts
and any related objects we might build tied tocase_contacts
The text was updated successfully, but these errors were encountered: