Roles and permissions

For instructions on managing roles and permissions, see the Manage roles and permissions page. For more information on managing project roles for groups of users, see the manage-groups page.

The table below shows the permissions associated with each CircleCI organization role:

Your CircleCI roles and associated permissions are not derived from the permissions set in your VCS (version control system). Your CircleCI role permissions do not allow you to bypass permissions in the VCS.

For example, you may be an Organization Administrator within CircleCI, which gives you access to view and modify organization and project settings within your CircleCI organization. However, you will not be able to edit a project’s .circleci/config.yml hosted in your VCS without your user also having the write permissions within that VCS’s repository project. Your CircleCI user’s VCS permissions are determined by its associated VCS identity.

Users can have roles assigned to them both individually and as part of a group. The highest role always applies. For example, if a user has the role of admin assigned for a project, and that user is also part of a group with the role of contributor for the project, the user will still have admin permissions for the project.