How to restrict functionality by group/role?
Status | NOT STARTED |
|---|---|
Stakeholders | |
Outcome | |
Due date | Jul 17, 2019 |
Owner | @Ian Ibbotson (Use this one) |
Related Features
UXPROD-1454 Restrict license management
Approach
Questions
What is the TC guidance on app-wide permission management?
Is there overlap or a pattern with Acquisitions development of Work Teams?
Any technical debt we’re accumulating wrt workflows and teams?
Impacts / Dependencies
External apps TBC
Action items
Comments
Jun 18, 2019
There's a significant difference between hiding from view (UI) and preventing access (backend). Are there really situations where hiding is sufficient (but that may not prevent direct or backend access).
Aggregating system permissions → permission blocks (logically useful functionality) → permission groups (assignable collections of permission blocks).
Separately, may need some means of aggregating users into privilege groups (to which you assign a permission group).