...
| Name | Includes | Access Granted | |
|---|---|---|---|
| Administrator | All permissions | Access to the entire administration section and every other aspect of Continua. Administrators are the only users that can modify global security settings | |
| Manage CI Server | Manage CI Agentsagents, all config. and build permissions | Access to the Continuous Integration Administration section. Users need this permission to modify CI properties and set CI Issue Connectors. This also includes agent management and all configuration and build functionality. (Note this permission does not include view project which is required to view configurations) | |
| Manage CI Agents | Access to the Agent administration section. Allows the user to authorise/deauthorise agents and delete agents | ||
| Project Administrator | All Project project permissions | Access to the Project security section. Also allows the user to create, edit and delete projects. | |
| View Project | Can see projects but cannot change any project settings. | ||
| Edit Project | View Projectproject | Can modify any settings on existing projects. This does not grant access to the Project Security project security section. | |
| Create Project | Edit Projectproject, View Projectview project | Can create new projects and edit existing projects. This does not grant access to the Project Security project security section. | |
| Delete Project | Edit Projectproject, View Projectview project | Can delete existing projects and edit existing projects. This does not grant access to the Project Security project security section. | |
| Configuration Administrator | All Configuration configuration and Build Permissionsbuild permissions | Grants full permission to configurations and builds. This also includes access to the Configuration Security configuration security section. (Note: to be able to view/modify a configuration, a user must also have View Project permissions on the configuration's parent project) | |
| View Configuration | Can see configurations and builds but cannot edit either the configuration or it's builds. This permission does not allow users to start or stop builds (Note: to be able to view/modify a configuration, a user must also have View Project permissions on the configuration's parent project) | ||
| Edit Configuration | View Configuration, All build permissions | Can modify any settings on existing configurations. This does not grant access to the configuration security section. This also includes all build permissions. (Note: to be able to view/modify a configuration, a user must also have View Project permissions on the configuration's parent project) | |
| Create Configuration | Edit configuration, view configuration and all build permissions | Can create new configurations and edit existing configurations, including all build actions. This does not grant access to the configuration security section. (Note: to be able to view/modify a configuration, a user must also have View Project permissions on the configuration's parent project) | |
| Delete Configuration | Edit configuration, view configuration and all build permissions | Can delete and edit existing configurations. This does not grant access to the configuration security section. This also includes all build permissions. (Note: to be able to view/modify a configuration, a user must also have View Project permissions on the configuration's parent project) | |
| Start Build | Can start builds. (Note: to be able to view builds, a user must also have view configuration permissions on the build's configuration) | ||
| Stop Build | Can stop builds. (Note: to be able to view builds, a user must also have view configuration permissions on the build's configuration) | ||
| Promote Stage | Can promote a build to the next stage. (Note: to be able to view builds, a user must also have view configuration permissions on the build's configuration) | ||
| View/Download Artifacts | Can view and download artifacts generated by a build. (Note: to be able to view builds, a user must also have view configuration permissions on the build's configuration) | ||
| Pin/Unpin Build | Can pin and unpin builds. (Note: to be able to view builds, a user must also have view configuration permissions on the build's configuration) | ||
| Add Comment | Can add and edit comments to builds. (Note: to be able to view builds, a user must also have view configuration permissions on the build's configuration) | ||
| Tag Builds | Can tag builds. (Note: to be able to view builds, a user must also have view configuration permissions on the build's configuration) |
Creating/Editing a Role
...
The permissions list contains every single permission in Continua grouped by category. The All permissions selected here are the ones you want the role to have access to.Take note that each category also has a check box which selects all the child permissionsthat are selected will be applied to the selected role. If a permission is grayed out, then this permission is being included from another permission. For example, if you select Projects then it will auto-select Create Project, Delete Project, Update Project and View Project. However, selecting Projects is an alias for Projects.*, so if a new permission was added, say Backup Project, then the role you've created will have permission for it. If, on the other hand you didn't select Projects and instead explicitly selected the Create/Delete/Update/View Project permissions then the role would not have permission to Backup Project.
Editing a Role
Clicking the "Edit" link at the end of each row will pop up a dialog with all the input fields needed to edit the selected role.
Clicking the "Delete" link at the end of each row will pop up a confirmation prompt. Click 'Yes' to delete the role.
edit configuration is selected then view configuration will also be selected as view is required to edit.
If a checkbox in the category header is selected then it will automatically check every permission in that category.
Once a role has been created it can then be linked to users and groups in the Access Control section.
Deleting Roles
When a role is deleted, all associated permissions are deleted with it. This means that deleting a role will strip it's permissions from any users associated to that role.
