Overview

Project permissions are used to control which actions a group of users may perform on a project. They can control at a fine level both the visibility of the project, along with who can configure and control it.

Permissions and Templating

It is important to understand the relationship between permissions and templates. In particular, the view permissions is reverse inherited: if a user can view a project this implies that they can also view all of its ancestors. See the Understanding Templates page for further details.

Project Actions

administer

This is a super action. Any groups granted the administer authority have complete access to all project actions.

cancel build

This action allows users to cancel a build of the project. The build may be queued, or may already have commenced (in which case it will be forcably terminated).

pause

This action allows the project to be paused and resumed. A paused project will ignore all build triggers.

trigger

This action allows a build of the project to be manually triggered.

view

This action allows the project to be viewed, including both the configuration and build results for the project. It is granted by default to all users and anonymous users (although anonymous access is disabled at the global level by default).

The view action is reverse inherited, see Understanding Templates for further details.

view source

This action allows working copy snapshots for the project to be browsed. As these snapshots will contain project source code, it may be desirable to prevent some users from viewing them.

write

This action allows the project configuration to be edited.

Global Actions

Global actions relating to projects, in particular the ability to create and delete projects, are assigned directly to groups. See Groups for details.