View source for Hudson-ci/features/Team Feature White Paper

== Hudson Teams White Paper ==

The Hudson Teams feature allows a single Hudson server to behave like multiple Hudson servers, each serving a project team within a single organization. By default, only jobs in a given team are visible to members of that team. In addition, job visibility across teams can be configured.

The Team feature is orthogonal to the configured <b>Security Realm</b>. 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 (which may be specific users or roles assigned to users via the security realm):

===== 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.  A user can be an administrator of multiple teams; in that case, 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.