Organize workspace members into groups

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

When you create a workspace, Bitbucket automatically creates an Administrators group and a Developers group. The users in the Administrators group are the members of your workspace you've specified as an admin. By default, all workspace members are in the Developers group.

Types of group permissions

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

Repository access

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

Admin

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.

None

Prevents those users from seeing anything in the repository.

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

Workspace member permissions

These permissions specify what the group's users can do within your workspace:

Create repositories

Allows workspace members to create new repositories for the team.

Administer team

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

Existing user groups

To find your workspaces's user groups, select the workspace from your avatar in the bottom left or click All workspaces for a full list. Click Settings, then select User groups. You'll see a list of the existing groups.

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.

Your workspace 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 workspace. 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 workspace 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 workspace'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. Click Save.

For your workspace'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 workspace owns by selecting All repositories that <your_workspace> owns.

  4. Select the new permission from the Access list.

  5. Click Update.

Update a group's permissions for the entire workspace

Workspace permissions give users the ability to update workspace settings or create repositories within the workspace.

  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 Workspace permissions option, select the checkboxes for Create repositories or Administer workspace to give or take away these permissions for this group.

  4. Click Save.

New user groups

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

From the User groups page, click Add group. Update the fields on the screen and click Add to save the group.

Field

Description

Name

Describes the type of users this group will include.

Default repository access

Specifies the group's default access when the team has a new repository:

  • Admin – 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.

  • None – Prevents those users from seeing anything in the repository.

Team permissions

Specifies what the group's users can do with the team account:

  • 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.

Admin notifications

(If this group has admin access) Specifies whether the groups's users will receive team notifications. You'll only be able to select this option if you also selected the Administer team permission.

When you click Add, the page for that group opens so that you can add users. Enter the user's name or email address and click Add. If you enter the email address of a non-user, that person receives an invitation to create an Atlassian account and join the team.

After you create a group, click Edit to update group permissions.

 

Last modified on Aug 11, 2020
Cached at 11:19 PM on Oct 20, 2020 |

Additional Help

Ask the Community