Team & Roles
Colony Cloud organizes access around two organization-level roles. Add and remove members from Settings → Members; changes take effect immediately.
Roles and permissions
Section titled “Roles and permissions”Every member of a Colony Cloud organization holds one of two roles:
| Role | Dashboard access | Repository management | Settings & billing | Member management |
|---|---|---|---|---|
| Member | Read-only | View only | No access | No access |
| Admin | Read-only | Enable / disable repos, configure pipeline | Full access | Invite, change role, remove |
A Member can view all dashboards and repository statuses. They cannot change any configuration, modify billing, or manage other members.
An Admin has full control over the organization, including settings, billing, and member management. The account that creates the organization is automatically an Admin.
Managing members
Section titled “Managing members”Invite a member
Section titled “Invite a member”- Open Settings → Members.
- Click Invite member.
- Enter the GitHub username or email address of the person you want to invite.
- Select a role: Member or Admin.
- 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
Section titled “Change a member’s role”- Open Settings → Members.
- Find the member in the Active tab.
- 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
Section titled “Remove a member”- Open Settings → Members.
- Find the member in the Active tab.
- Click the ⋯ menu next to their name and select Remove member.
- Confirm the dialog.
Removing a member revokes their access immediately. Their past activity (audit log entries, comments) is preserved.
Single sign-on
Section titled “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.