Introduction to Users, Roles, Teams, and Permissions
Release uses a role-based access control (RBAC) model. Teams can be defined on each folder, template, or release—for example, a Development team, a QA team, an OPS team, and a Release Management team—and permissions are assigned to those teams at the folder, template, and release levels. Permissions defined at the folder level are inherited by all templates and releases within it. Teams can also be configured directly on individual templates or releases that are not in a folder.
Understanding the concepts of Users, Roles, Teams, and Permissions is essential for effective administration and secure operation.
Users
A User is an individual who can log in to Release with valid credentials. Users can be managed internally within Release or externally via an Identity Provider (IDP) such as LDAP, Active Directory, or SSO solutions. Each user is uniquely identified by a username.
For more information, see User settings and Manage Users.
Roles
A Role is a way to group users who require similar access. Instead of assigning permissions to each user individually, permissions are assigned to roles, and users are added to those roles. This simplifies access management and ensures consistency.
For more information, see Configure roles.
Teams
A Team is a logical group of users, often organized by function or responsibility (e.g., Development, QA, Release Admin). Teams can be assigned permissions at the folder, template, or release level, allowing for flexible and granular access control.
For more information, see Configure release teams and permissions.
Permissions
Permissions define what actions users can perform in Release. Permissions are not assigned directly to users but are granted to roles and teams. Users inherit permissions through their assigned roles and team memberships.
For more information, see Configure permissions.
How These Concepts Work Together
- Users are assigned to roles and teams.
- Roles and teams are granted permissions.
- Permissions can be set globally (across the entire system) or scoped to specific folders, templates, or releases.
For detailed administration and advanced configuration, see Users and Permissions section of the Administration Guide.
Related Topics: