Skip to content

Sign In & Onboarding

Get Colony Cloud running for your organization. Sign in from your invitation, connect your code host, choose repositories, give Colony model access, run workers, and invite your team. Then follow the setup checklist on Work.

Colony Cloud is invitation-only. Colony creates your organization and sends its first owner an invitation. Owners and admins invite everyone else. Open the invitation link, then choose how to sign in.

  1. Open the link in your invitation email.
  2. Click Continue with your code-host account and authorize the Colony Cloud application when your code host prompts you. Colony Cloud reads your code-host identity and organization memberships. It does not access repository code at this step.
  1. Open the link in your invitation email. On the You have been invited page, click Create an account.
  2. Enter your Email, Display name and Password, then click Create account. You join the inviting organization and are signed in straight away.
  3. Check your inbox and follow the verification link to confirm your email address.

If you forget your password, click Forgot password? on the sign-in page and follow the emailed link to reset it. Once signed in, you can change your password under You → Sign-in (/you/sign-in).

The sign-in page explains what went wrong:

  • No invitation: “There’s no invitation for this account. Sign in with the account your invitation was sent to, or ask your Colony contact for one.”
  • Canceled on your code host: “Sign-in with your code host was canceled. Continue with your code-host account to try again.”
  • Expired link: “That sign-in link expired. Continue with your code-host account to start again.”
  • Anything else: “Sign-in with your code host didn’t complete. Try again in a moment.”

On the no-invitation message, click Use another account to sign out and start again. Your code host asks which account to use, so you can pick a different one.

An organization in Colony Cloud holds your worker capacity, billing, and repository connections. Colony creates it before you arrive, so there is nothing to set up. Your invitation takes you into your organization. As an owner, open Account → Tenants (/account/tenants) next to install the GitHub Apps.

If you already have an account and need another organization, Colony creates the organization and sends an invitation to your email. Accept it and the organization appears in your org switcher. Manage billing under Account → Billing (/account/billing).

Colony Cloud uses two separate GitHub Apps to interact with your repositories. Owners and admins install them from the Code host section of Account → Tenants (/account/tenants).

  1. In the Code host section, find the GitHub App install options. Installing colony-coder creates your tenant.
  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 the Code host section and 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.

Later, you can reach this page from Account → Tenants → your tenant → Repositories (/account/tenants/:tenantId/repositories). The old /settings/tenants link redirects to Account → Tenants (/account/tenants). Only organization owners and admins can install GitHub Apps. The MCP and CLI clients (OAuth connections) authorized for your organization are listed under Account → Connections (/account/connections), where you can revoke them. See Manage connections.

  • Only owners and admins can install. If you are a member, ask one of them to install the app.
  • The install link expired or was opened in another browser. Start the installation again from Account → Tenants.
  • The app was installed but Colony didn’t detect it. Connect the app again from the tenant’s Repositories page, or from Account → Tenants when there’s no tenant yet. Refresh only checks connections Colony already has.

Colony picks up proposals you authorize and items you mark for Colony. It doesn’t pick up every new item.

  • If the Repositories list is empty, grant colony-coder access to the repositories on GitHub, then click Check again.
  • If GitHub is unavailable, the page says so. That doesn’t mean you have no repositories. Try again in a moment.

Add your Anthropic API key under Operations → Settings (Secrets) (/operations/settings). See Secrets & keys. Saving checks the key with Anthropic first. A refused key isn’t saved. If Colony can’t reach Anthropic, the key is saved unchecked.

If your organization may use a Claude subscription instead, it is set per repository, in that repository’s Agent authentication drawer, not here.

If colony-coder is removed from your code-host organization while repositories are still enabled, Colony shows colony-coder was removed in the sidebar and on Operations, for everyone. Admins reinstall it from Account → Tenants. Members keep their access and ask an admin. Your settings are kept.

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

  1. Open Account → Members (/account/members).
  2. In the Invite Member form, enter the person’s Email address and choose a Role:
    • Owner: full control over the organization, including settings, billing, member management, and the ability to assign ownership. Colony invites the first Owner when it creates the organization.
    • 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.
  3. 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.

There is no separate setup wizard. Setup is a checklist on Work (/work), where the empty state would be. It has five steps: four to get Colony ready, then your first work item.

  1. Connect your code host
  2. Choose repositories
  3. Give Colony model access
  4. Workers
  5. Start your first work item

Each step names its owner, and only the next step you can do is highlighted. Click it to open a drawer with the same form that step lives in later. On a managed plan, Colony owns the workers step and completes it by itself once your workers register. On a plan with your own workers, an administrator runs them with a registration token.

Members see the checklist read-only, with the name of whoever owns each step. It updates by itself as steps are done.

While you have a required step you can do, a setup dot appears in the sidebar rail and on the tab that holds the step. Optional steps never show a dot.

Three optional steps sit under Whenever you like:

  • Invite your team
  • Add colony-operations
  • Set a monthly budget

When all five steps are done, the checklist folds away into a single line that lists any optional steps left. To start the autonomous pipeline, see Connect a Repository.