Role and Permission
Role is a set of permissions that can be granted to a user in one or all projects. A permission is an authorization granted to TeamCity user to perform particular operations.
Roles are assigned by the administrator on a per-project basis - a user can have different roles in different projects, and hence, the permissions are project-based. A user can have a role in a specific project or in all available projects, or no role at all. Depending on your TeamCity edition, different roles are available. You can associate a user account with a set of roles in the Assign Roles Dialog dialog.
Since TeamCIty 4.5 a role can also be granted to a user group. This means that the role is automatically granted to all the users that are included into the group (both directly or through other groups).
This section describes:
TeamCity Enterprise Edition User Roles
The roles and permissions are described and can be modified in the roles-config.xml file stored in <TeamCity Data Directory>/config directory. When assigning roles, the view role permissions link in the web UI displays a list of permissions for each role in accordance with how they have been manually re-configured.
Since TeamCity 4.5 set of roles and their permissions can be edited in the Administration web UI.
Role | Description and Permissions |
|---|---|
TeamCity System Administrators have no restrictions in their permissions, and have all of the project administrator's permissions. They can create and manage users accounts, authorize build agents and set up projects and build configurations, edit the TeamCity server settings, manage TeamCity licenses, configure server data cleanup rules, change shared VCS roots, and etc. | |
Project Administrator is a person who can customize the general settings of a project, build configuration settings and assign roles to the project users and has all the project developer's and agent manager's permissions. | |
Project Developer is a person who usually commits changes to a project. He can start/stop builds, reorder builds in the build queue, label the build sources, review agent details, take responsibility for the failed build. | |
Agent Manager is a person responsible for customizing and managing the Build Agent; he or she can change the run configuration policy and enable/disable build agents. | |
A Project Viewer has only read-only access for the projects the role is assigned to and can only view the project. Project Viewer role does not have permissions to view agent details. |
TeamCity Professional Edition User Roles
Role | Description |
|---|---|
TeamCity Administrators have no limitations in their permissions. They have access to all the projects, create users accounts, manage server licenses and set up projects and build configurations. | |
Common users correspond to "Project Developer" for all projects in the Enterprise edition. Users cannot create and edit projects and build configurations. |