WIP: Work In Progress Ticket. Tasks and Description will be updated. Attach all development branches to this ticket i.e., for each task, create a dev branch and link it to this ticket. Once all dev branches are created, this ticket will be consider completed.
Description
A team persona is a set of privileges granted to the user. This helps segregate work into specific teams, such as LLM and database teams, and enables seamless switching between these teams. It includes a Team Admin role for user management and theming. This feature enhances collaboration and organization by clearly defining team roles and responsibilities, improving overall productivity and team dynamics.
Existing/References
TBC
Tasks
[ ] Decide how to modify the current access or privilege granting system to teams
[ ] Update the security DB, smss_group table
[ ] Implement the ability for a user to select a team persona
[ ] Add users to a team persona
[ ] Implement a team/persona settings page
[ ] Implement CRUD operations for personas on the settings page
[ ] Add more tasks...
Questions to answer:
Who owns a group? Is it an admin, a team lead, etc?
How do users request access to a persona/group?
Where is group management done in the workflow?
How do different combinations of team personas and role personas overlap?
WIP: Work In Progress Ticket. Tasks and Description will be updated. Attach all development branches to this ticket i.e., for each task, create a dev branch and link it to this ticket. Once all dev branches are created, this ticket will be consider completed.
Description
A team persona is a set of privileges granted to the user. This helps segregate work into specific teams, such as LLM and database teams, and enables seamless switching between these teams. It includes a Team Admin role for user management and theming. This feature enhances collaboration and organization by clearly defining team roles and responsibilities, improving overall productivity and team dynamics.
Existing/References
TBC
Tasks
Questions to answer: