[Bamboo Knowledge Base]
There are several options for managing your Bamboo users and groups:
Note that the information on this page does not relate to application-level security for Bamboo – see Security instead.
To choose how you want to manage users in Bamboo:
Choose one of the user management options:
Manage locally in Bamboo
|Manage with Atlassian's JIRA applications||Allowing Other Applications to Connect to JIRA applications for User Management|
|Manage with Atlassian's Crowd||Integrating Bamboo with Crowd|
|Manage in a custom external user directory|
An author is any person who checks in code to a repository that is associated with a Bamboo plan. An author doesn't need to be a Bamboo user.
Depending on your organisation's requirements, you can configure Bamboo to grant access to non-users. However, only Bamboo users can:
Bamboo groups are used to specify which users will have global permissions and plan permissions. They can also be used to specify which users will receive notifications about a plan's build results. You can create and delete as many groups as you need. You will typically create at least one group per project. A special group called bamboo-admin is automatically created when you install Bamboo. Members of this group have Bamboo administration rights.
A special group called bamboo-admin is automatically created when you install Bamboo. Members of this group have Bamboo administration rights.
Bamboo permissions control access to plans, builds and administration functions. See Managing permissions.
A plan permission is the ability to perform a particular operation on a plan and its jobs. For each plan, different permissions can be granted to particular groups and/or users. A global permission is the ability to perform a particular operation in relation to Bamboo as a whole.