Access control for applications, repositories, and build artifacts
Concert applies role-based access control (RBAC) across applications, repositories, and build artifacts. Access to these assets is determined by the user’s role (L1 admin or L1 user) and their assigned access to specific applications or environments.
Applications
- Users and admins can view applications or environments for which they have access.
- Only users or admins with editor or L2 admin access can edit an application or environment.
Repositories and build artifacts
Access to repositories and build artifacts is derived from access to the applications or
environments they are associated with.
- Correlated: Repositories and build artifacts that are associated with an application or environment.
- Users who have access to the associated application or environment can view these correlated assets.
- Users without such access cannot view them.
- Uncorrelated: Repositories and build artifacts that are not associated with any
application or environment.
- L1 admins can view all uncorrelated repositories and build artifacts.
- L1 users can view only those uncorrelated repositories and build artifacts that they uploaded.
Access to repositories and build artifacts is derived from the RBAC permissions of the related
applications or environments. If a user gains view or edit access to an application or environment,
the same level of access extends automatically to the repositories and build artifacts associated
with that entity.
Note: The same access logic applies to both users and user groups. Access to
repositories and build artifacts is automatically aligned with the application or environment access
that has been assigned to the user or group.