Owners and Members

Set control and permissions to your collections.

Overview

To control access, Bluebricks separates account-level roles (which define what a user can do across the organization) from collection membership (which defines who belongs a specific collection). Together, these provide a balance between broad account privileges and fine-grained collection governance. By assigning members and owners, you define who can initiate or govern resources deployment to that collection.

Owners

Every collection must have at least one owner. Owners have full control over the collection, including:

• Managing member access and roles.

• Editing collection properties, secrets, and cloud connections.

• Transferring ownership if needed.

• Deleting the collection.

Owners provide the governance layer that ensures collections remain secure and aligned with organizational policies.

Admins always have the ability to manage collections, even if they are not listed as owners.

Members

Members are users who have been granted access to a collection. Their permissions depend on the account-level role they are assigned. Adding members allows teams to collaborate in a controlled way. For example, a development team may be added as contributors in a staging collection but only as viewers in production.

FAQ

Can a collection have multiple owners?

Yes, multiple owners can share responsibility.

Where do I manage member roles?

Admins can manage account-level roles (Admin, Builder, Deployer, Viewer) at the Account setting page → Members and define what a user can do across the entire account, while environment-level access is managed in Environment settings → Members, where environment owners (or Admins) decide who can access a specific environment and what role they hold within it.

Is there a limit for how many owners or members I can assign?

There is no fixed limit on the number of owners or members you can assign. An environment can have multiple owners for redundancy and as many members as needed to support collaboration. However, for security and governance, it’s recommended to keep ownership restricted to a small group while granting broader access through member roles.