Stakeholder Feedback: Define User Access Levels (UAL)

[JackHaeg]

Overview

Currently, user access levels (UAL) have yet to be fully defined in relation to the permissions provided to each UAL within the updated project details flow. In the future, multiple views / functionality on the project details screen will be provided depending on UAL.

Action Items

• Define the UALs listed below
• Define UAL privilages and views:
  • Project details
  • Projects (within the projects list screen)

Resources/Instructions

Figma VRMS

Example of Project management screen that will display different functionality depending on UAL

UAL

1. UAL0 - General volunteer

• I have joined HfLA, but not a team
• I CAN browse the projects and access general information.
• I CANNOT access files or team contributors’ info

2. UAL1 - Project members

• I have joined a project in HfLA
• I CAN access files and limited team contributors’ info
• I CANNOT make any changes to project data or members

3. UAL2 - Jr. Lead:

• I CAN create new events within my team
• I CAN access files and team contributors’ info
• I CANNOT make changes to project data and members

4. UAL3 - Leads:

• I am a lead or PM in my team
• I CAN create new events within my team
• I CAN access files and team contributors’ info
• I CAN make changes to project data and members

5. UAL4 - Admins:

• I am an admin at HfLA
• I CAN access files and team contributors’ info
• I CAN make changes to project data and members, INCLUDING project status (only admins can change this)
• I CAN create new projects or events
• I CAN onboard volunteers at HfLA

[JackHaeg]

@juliagab56 3rd issue to review. Please add the UALs, and feel free to add any additional information / remove the screenshot if it's not relevant :)

[JackHaeg]

@ExperimentsInHonesty to work on draft of this issue

[JackHaeg]

First section finished, to review second section when developing screens specific to UAL.