The platform needs a robust set of user and team management features, including:
Structure
The 'main' HOLPA interface will have multi-tenancy. Most users will be team members, and the main interface will be at the team level. For users with a single team, all pages are filtered to show only things related to that team. For users with multiple teams, they can switch between teams, but only ever interact with 1 team at a time.
There is also a 'program' level. A program is made of multiple teams, and intended for situations where there are multiple implementations of HOLPA that all fall under the same program or project.
For example, the implementation of HOLPA in 8 countries by the core team can be considered 1 program.
A user can be a member of many teams;
A team can be a part of a single 'program';
A program is a set of implementations of HOLPA led by a specific organisation/project/program. The idea is that program leads will have full access to all teams within the program. Team members would still only have access to their own team.
Site Admin Panel
[ ] A User Resource page where admins can:
See the full list of registered users, their roles and teams;
Send a password reset link to a specific user;
Suspend or delete a user;
Invite a new user with a specific site-wide role;
Invite a new user with to a specific team or program (and with a specific team-wide or program-wide role);
[ ] A Team Resource page where admins can:
See the full list of active teams, with space to show the 'status' of the team's progress with the HOLPA implementation.
Create new teams
Edit team information
Delete teams (?) - need to prevent this when there is actual information / data collected.
[ ] A Program Resource page where admins can:
See the full list of registered program.
Create new programs, and create multiple teams for a program,
Edit program information
Delete programs (?) - need to prevent this when there is actual information / data collected.
Program Admin Panel
[ ] A team and user resource similar to the above.
[ ] The ability to edit the current program information.
Team Panel
[ ] A user resource similar to the above.
[ ] The ability to edit the current team information.
The platform needs a robust set of user and team management features, including:
Structure
The 'main' HOLPA interface will have multi-tenancy. Most users will be team members, and the main interface will be at the team level. For users with a single team, all pages are filtered to show only things related to that team. For users with multiple teams, they can switch between teams, but only ever interact with 1 team at a time.
There is also a 'program' level. A program is made of multiple teams, and intended for situations where there are multiple implementations of HOLPA that all fall under the same program or project.
For example, the implementation of HOLPA in 8 countries by the core team can be considered 1 program.
A user can be a member of many teams; A team can be a part of a single 'program'; A program is a set of implementations of HOLPA led by a specific organisation/project/program. The idea is that program leads will have full access to all teams within the program. Team members would still only have access to their own team.
Site Admin Panel
[ ] A User Resource page where admins can:
[ ] A Team Resource page where admins can:
[ ] A Program Resource page where admins can:
Program Admin Panel
Team Panel