Sign Up & Onboarding

Get Colony Cloud running for your organization in four steps. Each step is self-contained and must be completed in order.

Create an account

1. Go to runcolony.com and click Sign in with GitHub.
2. Authorize the Colony Cloud application when GitHub prompts you. Colony Cloud reads your GitHub identity and organization memberships — it does not access repository code at this step.
3. After authorization, you land on the account creation screen. Enter your name and accept the terms of service, then click Create account.

Note

Colony Cloud uses GitHub OAuth for authentication. There is no separate username/password — your GitHub account is your identity.

Create an organization

An organization in Colony Cloud maps to a GitHub organization or a personal account you want to manage with Colony. Worker capacity, billing, and repository connections are all scoped to an organization.

1. After account creation, click New organization on the dashboard.
2. Enter an organization name (shown in the UI) and an organization slug (used in URLs — lowercase letters, numbers, and hyphens only).
3. Select the GitHub account or organization you want Colony to manage. This is the account under which repositories will be connected.
4. Choose an initial seat count — the number of concurrent Worker slots your plan supports. You can change this later under Settings → Plan.
5. Click Create organization.

You are now the owner of the new organization. The dashboard shows your empty repository list.

Install the GitHub Apps

Colony Cloud uses two separate GitHub Apps to interact with your repositories. Install them from Settings → VCS Connections inside Colony Cloud.

1. In Colony Cloud, open Settings → VCS Connections.
2. Click Install colony-coder and follow the GitHub App installation flow. Select the repositories (or the whole organization) you want Colony to have access to. This app is required — it grants Colony the permissions it needs to read code, open branches, create pull requests, and merge.
3. After colony-coder installs, return to Settings → VCS Connections and click Install colony-operations. This app is optional — it grants Colony the ability to manage issues, assign labels, and participate in code reviews. Install it to unlock the full autonomous pipeline, including issue triage and review management.
4. Confirm that both apps show a Connected status on the VCS Connections page.

Tip

You can skip colony-operations and install it later. Colony will still develop and merge code with colony-coder alone — you simply won’t have automated issue triage or review management until colony-operations is connected.

Caution

The two-step installation is intentional. colony-coder and colony-operations request different permission sets. GitHub requires separate installations so you can grant each scope independently and audit them separately.

Invite your team

Add team members to the organization so they can collaborate on repositories, view dashboards, and manage settings.

1. Open Settings → Members.
2. Click Invite member and enter the GitHub username or email address of the person you want to invite.
3. Choose a role:
   • Owner — full control over the organization, including settings, billing, member management, and the ability to assign ownership. The org creator is automatically an Owner.
   • Admin — full access including settings, billing, and member management; cannot assign or remove the Owner role.
   • Member — full dashboards and pipeline writes (file issues, pause, cancel); no access to settings or member management.
   • Viewer — read-only access to dashboards and pipeline data; cannot mutate state.
4. Click Send invite. The invitee receives an email and must accept before they can access the organization.

For the full permissions matrix, see Team & Roles.

Once your team is set up, connect your first repository to start the autonomous pipeline. See Connect a Repository.