Managing users
This page describes procedures for managing your Bamboo users locally in Bamboo.
For an brief overview of other options for managing your Bamboo users see Users and permissions.
このページの内容
参考資料
新しいユーザー アカウントの作成
Bamboo users can:
Depending on your organization's requirements, you can also configure Bamboo to grant access to non-users.
To create a Bamboo user:
- Click the
icon in the Bamboo header and choose Overview. - Click Users in the left navigation panel (under 'Security').
Complete the 'Add User' form:
Username
Username cannot be changed after the user is created.
Password
The user can easily change their password later.
Email
The address to which notifications are sent.
Instant Messaging Address
If no IM address is specified, Bamboo will not be able to recognize the user's context when interacting using IM.
Source Repository Aliases
If the user is a Bamboo author, click Add Alias to enter the user's login name for their source-code repository.
If you don't know their login name, they can specify it themselves later.
Change a user's password or details
To change a user's password or details:
- Click the icon in the Bamboo header and choose Overview.
- Click Users in the left panel (under 'Security').
- Locate the user by typing part of their username, full name or email, and clicking Search.
- Click Edit for the required user.
- Edit the user's details or password as necessary.
- If you have configured SMTP email on your Bamboo server, the user will automatically receive an email containing their new password.
- The user can easily change their password later.
- 保存をクリックします。
注意:
- Users who have forgotten their passwords can click the Forgotten your password? link on the Bamboo login screen. This will automatically generate a new password and email it to them (provided the Bamboo server has been configured to send SMTP email).
- Logged-in users can change their own password and details, as described in Managing your user profile.
- See Associating your author name with your user profile for information about Source Repository Aliases.