Team & Roles

Colony Cloud organizes access around four organization-level roles. Add and remove members from Settings → Members; changes take effect immediately.

Roles and permissions

Every member of a Colony Cloud organization holds one of four roles:

Role	Dashboard access	Repository management	Settings & billing	Member management	Notes
Owner	Full	Enable / disable repos, configure pipeline	Full access	Invite, change role (incl. owner), remove	Cannot remove the last owner; assigned automatically to the org creator
Admin	Full	Enable / disable repos, configure pipeline	Full access	Invite, change role (excl. owner), remove	Cannot assign or remove the owner role
Member	Full	View only	No access	No access	Can trigger pipeline writes (e.g. file an issue, pause, cancel)
Viewer	Read-only	View only	No access	No access	Read-only access to dashboards and pipeline data; cannot mutate state

An Owner has full control over the organization, including settings, billing, member management, and the ability to transfer or assign ownership. The account that creates the organization is automatically an Owner.

An Admin has nearly the same authority as an Owner but cannot assign or remove the owner role.

A Member can view all dashboards and trigger pipeline actions (file issues, pause or cancel runs) but cannot change configuration, billing, or manage other members.

A Viewer has read-only access to dashboards and pipeline data. Viewers cannot perform any writes — they can inspect pipeline state (e.g. via MCP colony_status) but cannot mutate it.

Note

Colony Cloud roles control access to the Colony Cloud dashboard and API. They are separate from the Colony pipeline roles (Operator, Author, Reviewer, Sponsor) that govern how Colony interacts with your code. See Operator, Author, Reviewer, and Sponsor for pipeline role guidance.

Managing members

Invite a member

1. Open Settings → Members.
2. Click Invite member.
3. Enter the GitHub username or email address of the person you want to invite.
4. Select a role: Owner, Admin, Member, or Viewer.
5. Click Send invite. The invitee receives an email and must accept before they can access the organization.

Pending invites appear in the Pending tab until accepted or expired. Invites expire after 7 days; resend them from the same tab.

Change a member’s role

1. Open Settings → Members.
2. Find the member in the Active tab.
3. Click the role badge next to their name and select the new role.

The change takes effect immediately. The member does not need to sign out and back in.

Remove a member

1. Open Settings → Members.
2. Find the member in the Active tab.
3. Click the ⋯ menu next to their name and select Remove member.
4. Confirm the dialog.

Removing a member revokes their access immediately. Their past activity (audit log entries, comments) is preserved.

Caution

You cannot remove the last Owner in an organization. Promote another member to Owner first.

Single sign-on

Colony Cloud uses GitHub OAuth as the primary authentication mechanism — there is no separate username/password. Members sign in with the GitHub account they used when accepting their invite.

Organization-level SSO (SAML/OIDC through your identity provider) is available as an Enterprise add-on. Per-IdP setup guides are published as each provider is supported. Contact your account manager to enable SSO for your organization.

Note

When SSO is enabled, members who have not linked their GitHub account to your IdP are blocked from signing in. Provision all members through your IdP before enabling SSO enforcement.