Organize your team into user groups

User groups help you organize your team into groups of developer feature teams or by roles. These groups allow you to manage access to your team's repositories and settings.

I just created a team.

When you create a team, Bitbucket automatically creates an Administrators group and a Developers group. The users in the Administrators group are whoever you specified as an admin during team creation. By default, all team members are in the Developers group.

Types of group permissions

A user group has two different types of permissions: default repository access and team update permissions.

Repository access

These permissions specify the group's access to a repository:

管理 Allows users to do everything a repository owner can do: change repository settings, update user permissions, and delete the repository.
Write Allows users to contribute to the repository by pushing changes directly.
Read Allows users to view, clone, and fork the repository code but not push changes. Read access also allows users to create issues, comment on issues, and edit wiki pages.
なし Prevents those users from seeing anything in the repository.

You can update a group's repository access permissions for future or existing repositories.


チーム アカウントでグループのユーザーが実行できる内容を指定します。

Create repositories Allows team members to create new repositories for the team.
Administer team

Allows team members to update the team's settings and the settings of any team-owned repositories.

You can update a group permissions for the team.

Existing user groups

To find your team's user groups, select your team from your avatar in the bottom left or click View all teams for a full list. Click Settings, then select User groups. You'll see a list of the existing groups, similar to the following example.

When you delete a group, that group no longer has access to any repositories it previously had. As a result, all group members lose access too unless they're part of another group with access.

Click one of the user group links and you'll see the permissions, members, and repositories associated with that group. You can also add and remove users from here.

To add a userenter the username or email address in the text box under Members, and then click Add.

To remove a user from the group, click x on the same line as the user. If the user isn't part of any other groups in the team, clicking x also removes the user from the team.

To edit the group's default repository or team permissions, click the Edit button. See the next two sections for more information.

Your team account plan includes the group members, which means that if you add a user to a User group, that user becomes a member of your team. If an account goes over the plan limit, you must remove members from a group or remove access from individual repositories until the account is back within its plan limits. For information on repository access, see Grant access to team repositories.

Update a group's repository access permissions

You can change group access for future or existing repositories. When you update access for a group from the Edit button, all future repositories will have the new permissions but not existing repositories. As a result, if you want to change group permissions for everything, you need to do both sets of steps in this section.

For your team's future repositories:

  1. From User groups, click the name of the group you want to update.
  2. Click Edit in the top-right of the group's page.
  3. From the Default repository access dropdown, choose the permission you want.
  4. 保存をクリックします。

For your team's existing repositories:

  1. From User groups, click the name of the group you want to update.
  2. Click More in the top-right of the group's page, and choose Update repository access.
  3. By default, Repositories this group can currently access is selected. Keep it this way if you just want to update repositories that group has access to. You can also add this group to all existing repositories the team owns by selecting All repositories that <your_team> owns.
  4. Select the new permission from the Access list.
  5. [更新] をクリックします。

Update a group's team permissions

Team permissions give users the ability to update team settings or create team repositories.

  1. From User groups, click the name of the group you want to update.
  2. Click Edit in the top right corner of the group's page.
  3. From the Team Permissions option, select the checkboxes for Create repositories or Administer team to give or take away these permissions for this group.
  4. 保存をクリックします。

New user groups

When you create a group, you specify the type of permissions you want to give group members for the team and for newly created repositories.

  1. From the User groups page, click Add group.
  2. Enter a Name for your group. You can create a new group or use an existing group. If you're adding an existing group to your team, start typing and the group name will auto-populate.
  3. Select Default repository access for the group. These permissions specify the group's default access when the team has a new repository:
    • 管理者 – ユーザーは、リポジトリの所有者が実行できるすべての作業 (リポジトリの設定変更、ユーザー権限の更新、およびリポジトリ削除) を実行できます。
    • 書き込み – ユーザーは、リポジトリに変更を直接プッシュできます。
    • 読み取り – ユーザーは、リポジトリ コードの表示、クローン、フォークはできますが、変更のプッシュはできません。読み取りアクセス権が付与されると、ユーザーは、課題の作成、課題へのコメント、および Wiki ページの編集も行えます。
    • なし – ユーザーは、リポジトリ内の内容を見ることはできません。
  4. Select Team Permissions for the group. These permissions specify what the group's users can do with your team account:
    • リポジトリの作成 – チーム メンバーがチームに新しいリポジトリを作成できるようにします。
    • チームの管理 – チーム メンバーがチームの設定とチームが所有するリポジトリの設定を更新できるようにします。
  5. Click Add to save the group.
  6. The page for that group opens. Here's where you add users. Enter their username or email address and click Add. If you add a member via email, Bitbucket sends an email inviting them to join your team.

After you create a group, you can see its permissions on the group page. Green check marks show permissions that user group has and gray negative marks show permissions the group doesn't have. Click Edit to update group permissions.

Example: Create a group for contractors

Let's say you want to provide Read access to all of your repositories for external contractors. When you create a Contractors group, the Add group dialog would look something like this:

From the Contractors group page, your permissions would look like this:

Example: Distinguish between repository and team permissions

You can allow users to create repositories for the team without giving them any sort of admin permissions. To do this, set Team permissions to Create repositories while their Default repository access is set to Write. Users in this group cannot administer the team account, but they can create repositories for the team.

最終更新日 2017 年 5 月 30 日


Powered by Confluence and Scroll Viewport.