Difference between revisions of "Hudson-ci/features/Team Feature White Paper"
(New page: == Hudson Teams White Paper == Hudson Teams allows a single Hudson server to behave like multiple Hudson servers, each serving a project team within a single organization. The Team featu...) |
m (→System Administrator) |
||
| Line 11: | Line 11: | ||
==== System Administrator ==== | ==== System Administrator ==== | ||
| − | A system administrator can manage Hudson, create and delete teams, move jobs from team to team, and administer team privileges. In particular, a system administrator can delegate team | + | A system administrator can manage Hudson, create and delete teams, move jobs from team to team, and administer team privileges. In particular, a system administrator can delegate team administration responsibilities to team administrators. |
==== Team Administrator ==== | ==== Team Administrator ==== | ||
Revision as of 22:40, 15 July 2013
Contents
Hudson Teams White Paper
Hudson Teams allows a single Hudson server to behave like multiple Hudson servers, each serving a project team within a single organization.
The Team feature is orthogonal to the configured Security Realm. It honors roles assigned to users and in many ways simplifies the administration of team-aware permissions.
Team Users
There are three categories of team users:
System Administrator
A system administrator can manage Hudson, create and delete teams, move jobs from team to team, and administer team privileges. In particular, a system administrator can delegate team administration responsibilities to team administrators.
Team Administrator
A team administrator can add new members to the team, including administrator members, and assign them job create, delete, configure and build privileges, separately. If a user manages multiple teams, the user can move jobs from team to team.
Team Member
A team member can perform the actions granted by a system or team administrator. A user can be a member of multiple teams.