How users accumulate on a team

How users accumulate on your plan

Each user given access to a private repository counts to your plan. If you give others administrator permission to your private repositories, they can add and remove users too. When administrators give a new user access to a private repository, Bitbucket Cloud checks the repository owner account and increments the plan count. 

When you are on the free plan and you add users which exceed the 5 user limit you will be prompted to upgrade your plan in order to add additional users.

The team owner or administrator can increase the plan. Or, administrators can remove excess users to reduce the user count  limit. Once your account is within its plan limit, everyone's access returns to normal.

Creating a clear set of guidelines for team and team repository administrators is essential to good user management.

Those who administer your team or team repositories can add groups which are not part of your team to repositories owned by your team. While this function is very useful to build community around a public repository it is problematic for private repositories.

All the users in a group added to your team's private repositories count as part of your team user plan. The best way to add users to a team is to create a group in that team and invite those users to that group. This provides clarity into both the user count and user management (who has access to what) which is critical to running an effective project.

Teams in Space scenario

This is the story of how the Teams in Space team grew over time and how, as the team added users, that impacts the plan the team needs.

What happens How this looks in the team                                      

Jackie creates Teams in Space, invites Tim and Sara, and creates the secret sauce repository.

Now Teams in Space has three members so the team is on the free plan.

The team creates a new repository, and invites Shawn to the Developers group.

Now Teams in Space has four members and is still on the free plan.

The team creates another group for contractors which they want to limit to a single repository. They invite Lynn, Jamie, and Tam to this group.

Now Teams in Space has 7 members and will need to upgrade to a 10 user plan.

If a team administrator does this: Then the number of users counted for billing will be:
Adds another user.

There would be 8 users so there would not be any change to the plan.

Because the plan this team is on allows up to 10 users they can add three users before needing to upgrade to the 25 user plan.

Makes the Plug-in repository public

Now there would only be 4 users with access to the teams private repositories.

This would allow the team to revert to the free plan.

Removes the contractor group

This would remove 3 users from the plan so the team would have 4 users and could revert to the free plan.

Some things to remember:

  • Users always only count once: so Anne can be a member of both repositories and will always only count as 1 user against the billing plan for this account. She can, however, also count as 1 user in another person or team's billing plan if that person or team has invited her to a private repository.
  • Changing a repositories status changes the status of all the users in that repository: It's the repository state (private or public) which matters in counting users against your billing plan. So you should consider any groups with access to a repository, especially when changing it from public to private.
  • Groups bring all their users with them when you add them to a repository: When you invite a group to your repository all the users in that group count against your billing plan. If you only want some of the members of a group to count you must add them individually, adjust the group by removing or adding members, or create a new group with only those you wish to count.
  • Giving someone repository administrator rights to a private repository will allow them to invite users to that repository and those users will count against your billing plan.

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport