Team & Roles
Colony Cloud organizes access around four organization-level roles. Add and remove members from Account → Members; changes take effect immediately.
Roles and permissions
Section titled “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; the first owner is invited when the organization is created |
| 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 first Owner is invited when the organization is created.
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_work with view=status) but cannot mutate it.
Grants
Section titled “Grants”Behind the four roles, Colony Cloud stores access as grants. A role is a name for a common grant; Colony derives a member’s role from their grants rather than storing it. Every member also holds the baseline: read access to dashboards and pipeline data.
A grant has three independent parts:
- Administration reach:
org-administrator,tenant-administratoror none. It decides who may administer the account itself, and how far. - Bundles: any of Standards, Autonomy, Operations and Reporting. Each bundle adds the ability to change one kind of thing.
- VCS write: whether the person may act on work items, using their own VCS credential.
A grant can also carry a tenant scope. A grant with no scope is org-wide: it covers every tenant in the organization, including tenants added later. A scoped grant covers one tenant only.
Roles and the grants they confer
Section titled “Roles and the grants they confer”| Role | Administration | Bundles | VCS write | Scope |
|---|---|---|---|---|
| Owner | org-administrator | All four | Yes | Org-wide |
| Admin | tenant-administrator | All four | Yes | Org-wide |
| Member | None | None | Yes | Org-wide |
| Viewer | None | None | No | Baseline only |
What each bundle unlocks
Section titled “What each bundle unlocks”| Bundle | Unlocks |
|---|---|
| Standards | Conventions and standards (conventions-update, standard-create, standard-update), standards sets (standards-set-create, standards-set-publish, standards-subscription-update, standards-exception-write), workflow authoring (workflow-definition-create), inherited-setting bindings (setting-binding-standards-write), and intelligence approval (intelligence-approve, intelligence-dismiss, intelligence-patch, knowledge-add) |
| Autonomy | Self-improvement tracks (si-track-create, si-track-update, si-track-delete, track-update), track prompts and governance (si-track-prompt-create, si-track-prompt-activate, si-track-governance-update), portfolios (si-portfolio-draft-write, si-portfolio-publish, si-portfolio-activate, si-portfolio-template-write), charters (charter-update), automations (automation-update), strategy runs and snapshots (colony-strategy, snapshot-generate, snapshot-approve, snapshot-reject, snapshot-revert), the repo’s autonomy grant (autonomy-grant-update) and inherited-setting bindings (setting-binding-autonomy-write) |
| Operations | Inherited-setting bindings (setting-binding-operations-write), repo secrets and credentials (repo-secret-write, repo-credential-write, repo-oauth-credential-write, repo-credential-read), Workers and tokens (worker-update, worker-drain, worker-reclaim, worker-token-create, worker-token-revoke, worker-token-list-read, api-token-create, api-token-revoke, api-token-list-read, worker-floor-read, worker-list-read, worker-llm-health-read), outbound webhooks (outbound-webhook-create, outbound-webhook-update, outbound-webhook-delete, outbound-webhook-test, outbound-webhook-delivery-replay), dead-letter and write-queue recovery (dead-letter-retry, dead-letter-resolve, dead-letter-resolve-all, vcs-projection-retry, vcs-projection-discard), the fault ledger (fault-acknowledge, fault-mute, patience-update), repo settings (repo-settings-update), and the transition overrides (unblock, skip-planning, state) |
| Reporting | Inviting and removing report readers (report-reader-invite, report-reader-remove) |
On the Operations fault ledger, acknowledging a fault marks it as seen by someone, and muting it quiets it so it stops competing for attention. Reading the ledger is part of administration, not of the bundle.
The ledger has two kinds that come from the patience ladder:
- An ask went unanswered (
ask-unanswered): an ask or manual block reached its repository’s fault rung. - Work has nobody to tell (
nobody-to-tell): an item with no steward, no default steward and nobody who worked in the repository for 14 days. The remedy is to name a default steward.
Work actions need VCS write, plus write access to the repository on your code host: pause, resume, cancel, retry, plan-import, draft-publish, work-item-comment-create and the like. A Member can take them without holding any bundle.
The Reporting bundle gates inviting and removing report readers, the people who read sealed reports and nothing else. Reporting pages are readable under the baseline, and any member can see the list of readers. Owners and Admins hold the bundle.
Administration reach
Section titled “Administration reach”org-administratorcarriesorg-delete,org-audit-log-read,org-member-promote-to-ownerandworker-pool-update. Owners hold it.tenant-administratorcarries member and invitation management (org-update,org-member-update,org-member-remove,org-member-sign-out,org-member-suspend,org-invitation-create,org-invitation-list,org-invitation-revoke), org secrets (org-secrets-read,org-secrets-write), repository env secrets (repo-env-secret-write), org pipeline config and onboarding (org-tenants-read,org-pipeline-config-read,org-pipeline-config-update,org-pipeline-discover,org-pipeline-adopt,org-onboarding-dismiss), connections (org-connection-health-read,org-connection-revoke-any,org-connection-policy-update), chat (chat-connection-manage), billing (billing-read,billing-customer-create,billing-invoices-read,billing-invoice-read,billing-payment-method-read,billing-tenants-read,billing-tenant-read,billing-tenant-checkout,billing-tenant-tier-update,billing-tenant-cancel,billing-tenant-reactivate,billing-tenant-workers-update), installations (installation-list-read,installation-connectable-read,installation-refresh,installation-connect,installation-disconnect,installation-repo-update,repo-default-steward-update), repository groups (repo-group-write: create, edit, delete, reorder and preview), the daily cost cap (daily-cost-cap-update: set it or raise it for today, with a reason) and the Worker pool (worker-pool-read). Admins hold it.
Holding a bundle does not confer administration, and the reverse is also true. That is why owning Standards does not mean holding billing.
The dashboard does not edit grants directly today. Members get them through the role chosen when you invite them or change their role on Account → Members, which replaces their grants with the ones that role confers. The Members page shows each person’s grant summary.
Report readers
Section titled “Report readers”A report reader is someone who reads sealed reports and nothing else, such as a finance or delivery lead.
- They are invited by email and need no code-host account. They can register with an email and password.
- They read the sealed reports of every tenant in the organization, and Colony’s reading of each.
- They are not members. They hold no baseline and no grants, and they do not appear on Account → Members.
- They can subscribe to report emails.
Anyone with the Reporting bundle can invite a report reader from Share or export on a sealed report, or from Reporting → Settings (/reporting/settings), and remove one there. Removing a report reader signs them out. To make a report reader a member, remove them and invite them again.
Managing members
Section titled “Managing members”Invite a member
Section titled “Invite a member”- Open Account → Members.
- In the Invite Member section, enter the invitee’s Email address. The dashboard invites by email only.
- Pick a Role: owner, admin, member, or viewer. The default is member. A hint under Role explains the role you have selected.
- Click Send Invite. The invitee receives an email and must accept before they can access the organization.
Invitations appear under Pending Invitations, each with its role and expiry date, until they’re accepted or expire. Invitations expire after 7 days.
There’s no resend action. To resend, click Revoke on the invitation, confirm the dialog, and invite the person again.
Change a member’s role
Section titled “Change a member’s role”- Open Account → Members.
- Find the member in the Current Members section.
- Use the role select on their row to choose the new role.
- In the Change role dialog, check the details and click Change role. The dialog names the member, the new role and the organization, and adds a one-sentence consequence, for example that a viewer loses the ability to change settings or act on work. Click Cancel to keep the current role. A Role updated toast confirms the change.
The role changes only after you click Change role.
Changing a role needs the org-member-update capability. Without it, the role select on the row is inert and shows the reason. Promoting someone to Owner also needs org-member-promote-to-owner, which the org-administrator grant carries.
A role (grant) change ends the member’s sessions, and they sign in again to pick up the new role. If you change your own role, your current session stays signed in.
Remove a member
Section titled “Remove a member”- Open Account → Members.
- Find the member in the Current Members section.
- Click Remove on their row.
- In the Remove member dialog, type the member’s name as shown on their row (their display name, or their email address if they have none). Remove member permanently stays disabled until it matches.
Removing a member revokes their access immediately, in one step. Removal revokes:
- every session the person holds, in every organization (they sign in again);
- every connection (MCP/CLI) token they hold in this organization. Their connections in other organizations are untouched;
- their stored GitHub token, only when they belong to no other organization. Their GitHub identity link is kept, so signing in with GitHub again restores the token.
The audit log records one member.removed entry that lists what was revoked. Their past activity (audit log entries, comments) is preserved.
Row actions
Section titled “Row actions”Each row in Current Members has a role select (see Change a member’s role), Sign out, Suspend (or Reinstate for a suspended member; your own row has no Suspend) and Remove. When you don’t hold the capability an action needs, the control is inert and shows the reason.
Sign a member out
Section titled “Sign a member out”To end a person’s sessions without removing them, sign them out. This needs the tenant-administrator grant (capability org-member-sign-out).
Signing a member out ends every session they hold, in every organization. They sign in again to continue. It does not revoke their connection tokens; only removal does that.
The audit log records a member.signed_out entry. The endpoint is POST /api/orgs/{orgId}/members/{userId}/sign-out; it returns 404 unless the person is a member of that organization.
Suspend a member
Section titled “Suspend a member”To stop a person’s access without destroying it, suspend them. This needs the tenant-administrator grant (capability org-member-suspend). Open Account → Members, click Suspend on the member’s row, enter a reason, and confirm. The reason is required.
A suspended member loses access to this organization immediately:
- session requests to the organization’s pages and API are refused;
- they cannot switch into the organization, and it drops out of their organization switcher;
- their MCP/CLI connection tokens for the organization are refused;
- they receive no notifications for the organization.
Suspending also signs them out of every organization, because it bumps their session epoch, as removal and force sign-out do. On their next sign-in they land in another organization, or in none.
Suspension keeps their membership, their grants and their connected MCP/CLI clients. The clients are refused, not revoked.
Click Reinstate on the suspended member’s row to restore access as it was. There is no re-invite, no grant rebuilding and no re-consent for connected clients. A suspended member can still be removed.
The audit log records a member.suspended entry, with the reason, and a member.reinstated entry on reinstatement.
The Members page also shows each person’s grant summary and when they last used their access (“Last used …” or “Never used”).
Audit log
Section titled “Audit log”The audit log is a chronological record of administrative actions in your organization. Open it from Account → Audit log (/account/audit-log).
Opening it needs the org-administrator grant (capability org-audit-log-read). Members without the grant see the Audit log entry disabled.
The page lists events newest first, in a table with these columns:
| Column | Shows |
|---|---|
| Actor | Who took the action |
| Action | What happened, for example member.removed |
| Target | The affected object, as targetType/targetId |
| Metadata | Extra detail as JSON, or — when there is none |
| Timestamp | When it happened, in your local time |
The page loads 50 events at a time. When the organization has more than 50 events, a “Showing X–Y of N” line appears with Previous and Next buttons. With no events, the page reads “No audit events recorded yet.”
There is no CSV export. For programmatic access, call GET /api/orgs/{orgId}/audit-log?limit=&offset=.
Examples of recorded actions include member.removed, member.signed_out, member.suspended, member.reinstated, and a webhook being automatically disabled.
Sign-in methods
Section titled “Sign-in methods”Colony Cloud has three sign-in paths: your code-host account, an email and password, or a magic link emailed to an existing account. Everyone starts from an invitation. See Onboarding for the flows and Account settings for changing your password.
Colony Cloud does not offer SAML or OIDC single sign-on today. Contact sales@runcolony.com if your organization requires it.