Groups

What this means

Groups give you finer access control inside an organization.

A group connects members to products. Members in the group inherit access to the products assigned to that group. Admins and owners can still access every product regardless of group membership.

When to use it

Use groups when:

• Not every developer should run pipelines on every product.
• You want a backend team, frontend team, mobile team, or customer-specific team to see only relevant products.
• You need to give temporary or scoped access.
• You want product access to be easier to review.

If your organization is small and every member can work on every product, you may not need groups yet.

Before you start

You need owner or admin access to create and manage groups.

Create products and invite members before you build group memberships. A group can be created empty, but it is only useful after members and products are added.

Group fields

Steps: create a group

1. Open Settings -> Groups.
2. Select New group.
3. Enter a name.
4. Add an optional description.
5. Create the group.
6. Open the group detail page.
7. Add members.
8. Add products.

Managing a group

On the group detail page you can:

• Edit the group name and description.
• Add existing organization members.
• Remove members from the group.
• Add products.
• Remove products from the group.

To add someone who is not listed, invite them from the Members page first.

What happens next

Members in the group can work with the products assigned to that group according to their role. Removing a member or product from a group changes access immediately.

Deleting a group removes the group and its membership rows. Existing pipelines stay in history.

Problems and fixes

Related pages

• Members
• Products
• Repositories
• Organizations and roles