-
Type:
Task
-
Status: Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: NoFixVersionApplicable
-
Component/s: Connect / Account Management
-
Epic Link:
-
Tags:
-
Story Points:3
Context: M3 treats the concept of user rights and user groups, it leads fairly directly to the notion of several services for one project. this does not currently exist and needs to be understood.
Currently, for one project, Connect will consider only the most recent. This could be changed.
Figma Link :
https://www.figma.com/file/y2uw7SQPzoTmWwlhFldx2B/Nexio-User-Management?node-id=124%3A4116
Aim: Can we evolve the current way that Connect services apply rights/access/contacts to projects? In particular the scenario several services applied to one project.
If a solution is proposed =>
- How are users identified as being part of x service?
- How are user roles resolved?
- Does having several create code issues?
- Does having several create performance issues?
- Other functionality issues in Connect