Account administration for the Maestro Project Server, which includes user account administration for the Project Server, the Artifact Repository Manager, and the Continuous Integration Server, allows you to add/edit/delete users and grant roles (privileges) to them.
The table below lists all the roles that can be assigned to a user. Accounts can only view what they have been given explicit access to. For example, if a user does not have System Administrator or User Administrator privileges, he will not see the Users button on any screen in Maestro. Another example, users only see projects that they have been granted rights to, so their view of Build Management's Projects screen will only show projects for which they have Project Developer or Project User roles.
When new project groups are added, they are automatically registered with the Continuum Group Project Administrator role. This takes effect immediately so if you are granted the System Administrator role then you are automatically granted access to all aspects of that project because the System Administrator role also effectively gives the account the Continuum Group Project Administrator role. Therefore, accounts with either System Administrator role or Continuum Group Project Administrator roles can also assign Project Developer role to another account giving it the ability to have influence over that particular project group.
One of the major benefits of this is that you can adjust the allocation of permissions to roles and never have to touch individual accounts if you setup the initial role structures in a reasonable fashion. And if you do have to work with an account it's simply the act of granting or removing roles, not dealing with the minutia of individual access lists. One way to think about this is that often the roles seem to be organized along the lines of "jobs" that one would perform.
For the Artifact Repository Manager, the "system administrator or root equivalent role is the Global Repository Manager, which is allowed to create, edit, and delete all repositories as well as manage content in all the repositories.
Accounts given System Administrator rights are effectively also given Continuum Group Project Administrator rights. This is not the case for the Global Repository Manager. Accounts must be explicitly granted this right.
User Account Roles
| Role | Description |
| Registered User | This role allows an individual to edit their own user information. An account with this role cannot add projects or perform any other account maintenance such as add/edit/deleting other users. |
| User Administrator | An account with this role can add/edit/delete user accounts. |
| System Administrator | An account with this role can add/edit/delete/build projects, add/edit/delete users, and add/edit/delete Maven repositories. This role also can manage the General Configuration of Maestro and run the Archiva reports. |
| Guest | This role allows an account to see limited options in the Project Server, Artifact Repository, and Build Management screens. |
| Continuum Group Project Administrator | This role gives you the ability to manage all project groups and perform all operations on project groups. With this role you don't have to be granted the Project Developer role per project. This role also allows you to assign Project Developer and Project User roles to other user accounts. |
| Continuum Group Project User | This role gives the user Project User rights to all projects. |
| Continuum Group Project Developer | This role gives the user Project Developer rights to all projects. This role can manage/edit the Continuum Configuration, Continuum Notifiers, and Continuum Schedules. |
| Continuum Manage Installations | Allows you to add, edit and delete different tools to build your project. Installations are the different tools (JDK, Maven, Ant, etc.) that a project requires. |
| Continuum Manage Build Environments | Allows you to add, edit and delete build environments to use with a build definition. A build environment is a pre-configured environment used with build definitions to change the default tool(s) to use. A build environment is composed of a set of installations. |
| Continuum Manage Queues | Allows you to view the build and checkout queues and to cancel jobs that are queued. The build queues show what projects are currently building or are queued to build. The checkout queue shows projects in the process of being checked out from SVN, CVS, or from the filesystem. |
| Continuum Manage Build Templates | Allows you to add, edit, and delete build templates. Build templates are pre-defined build goals that can be applied against your projects instead of manually defining the build goals for each project. By default Maestro supplies several templates which can be edited or deleted. Users with this role are also allowed to add, edit, and delete templates in addition to the default ones. |
| Continuum Manage Scheduling | Allows you to add, edit, and delete schedules for Continuum. These schedules are assigned to each project and determines when a particular project will automatically build. |
| Continuum Manage Purging | Allows you to manage the repository purging configurations for repository clean up. |
| Continuum Manage Repositories | Allows you to configure a specific repository to be used for a certain project. |
| Project Administrator - per project | This role is assigned per project and allows the account to assign people to the roles for that project but not to assign roles to other projects. This role must be explicitly granted to an account for each project. |
| Project Developer - per project | This role is assigned per project and allows the account to view, add/edit/delete, and build projects. User A could have Project Developer privileges on projects A, B, and C, but not on D. This role must be explicitly granted to an account for each project. |
| Project User - per project | This role allows the user to view the project and is assigned per project. |
| Global Repository Manager | This role allows administrative access to setup and maintain managed and proxied repositories as well as manage content in the repositories. |
| Global Repository Observer | This role allows complete access to read contents of all the repositories. |
| Repository Manager - per repository | This role allows the user to manage the content (add/edit/delete content) on a specific repository. |
| Repository Observer - per repository | This role allows the user to view reports for a specific repository. |
| Site Producer | This role allows the user to publish sites from Maven 2 projects into Maestro. |
| Site Observer | This role allows the user to click on the sites link and see the published site content. |
The diagram below shows the hierarchal layout of the roles. You can assign the roles specified in the diagram. Any of the roles that you assign, such as System Administrator, automatically give the user account the permissions of the child roles.
Note: In Maestro 1.5, you only see the roles for a particular subsystem when you click the Users button from that subsystem, for example, to see the project roles you must click Users from Build Management.