2.1. Users, Groups and Roles
rolloutMan is very functin aware software. Users, Groups and Roles are used to enforce this feature at different levels and lifecycles. This is a result of the strong implementation of security principles, details of which is covered in this section.
Refer link Define Users and Groups to learn more about managing users and groups.
A Group is a collection of Users, which have same roles in a rollout execution. Groups allow to manage movement of users in and out of a rollout, as people leave or join the company, team or releases.
Being a part of a Group, allows a rollout Task to be picked up by another member of the same team, just in case the team member is not available for performing a release activity.
Each group is closely tied into a User Type (or Role). This allows different groups - for development, administrators and operation support teams - for the same functionality.
We recommend defining groups in one of the following patterns:
- We recommend that groups are created for each applications & function. For e.g. for a CRM Application, the group could be CRMManagers(Observer Role), CRMUsers (User role) for Developers/ Deployment team, CRMAdministrators (Admin Role)
- Another approach is for creating a group per resource pool - for e.g. DBA's, Unix Admins etc. This allows these resource pools to be allocated for different projects.