Patterns
User Management
Design access and permissions control system (Admin Panel)
Status component contains a list of checks and completeness that has been tested and owned by each component
The use case of user management contains a collection of user management processes that are commonly found and collected from many sites. The use cases will provide examples of creating a granular model of user management that matches how many users would be in the company.
Case: Access Control List (ACL)
User Story: As an admin, I want to monitor and manage the permissions of users directly as I created the users so that I can save some time.
Requirement Scenario/Acceptance Criteria
- Provide specific control list of resources that can be accessed by users
- Provide control access to the permissions list of resources
- Able to create users directly within its permission control
- Provide edit and delete users to admin
- Able to manage the permissions of the users list
Pros and Cons
This pattern is a suitable choice for environments where there is a high chance of variation in access requirements.
This pattern is not suitable for managing complex resources and many types of users.
Case: Role Based Access Control (RBAC)
User story: As an admin, I want to monitor and manage permissions of roles for users in my company so that I can better assign users to each role.
Requirement Scenario/Acceptance Criteria
- Separate the list of roles and users in different tabs or pages
- Provide ability to create roles with specific permissions (e.g. view, update, hide, and more)
- Provide ability to assign users to specific roles when it’s created
- Provide information of how many users were assigned to their role
- Provide ability to edit and delete the roles and users
Pros and Cons
This pattern is suitable for environments where the number of users and features grow while only managing it by the roles & permissions
This pattern is not suitable for resources that require specific permissions.