Account (Profile, Linked accounts & Prerequisites)
The Profile, Notification log, Password and Linked accounts pages are personal account settings. They are available to every authenticated user regardless of their organization role — no Owner or Admin privileges are required. The Prerequisites checklist is different: it sits on Account → Tenants, which needs the tenant-administrator grant.
Access requirements
Section titled “Access requirements”| Who can access | Scope |
|---|---|
| Any authenticated user | Own account only |
Profile
Section titled “Profile”Open You → Profile (/you/profile) to update your display name. Notification preferences are on their own tab, You → Notifications (/you/notifications).
Fields
Section titled “Fields”| Field | Required | Constraints | Description |
|---|---|---|---|
| Display Name | Yes | Max 100 characters | The name shown in the Colony Cloud dashboard. If you signed up with GitHub, it starts as your GitHub name or username. An account with no display name shows its email address instead. |
Unsaved changes
Section titled “Unsaved changes”Navigating away from the Profile page with unsaved edits prompts a confirmation dialog — “Discard unsaved changes?”, “Your unsaved profile changes will be lost.” — before discarding your work.
You › Notifications
Section titled “You › Notifications”You → Notifications (/you/notifications) holds everything about how Colony points you at work.
How you’re told. One choice for everything; Colony never sends the same thing twice.
| Mode | What you get |
|---|---|
| Live | A pointer each time something new is waiting for you. |
| Edge (default) | One pointer when your queue goes from empty to waiting, at most once an hour. |
| Digest | What arrived, in one message, hourly or daily. Nothing new, nothing sent. |
| Off | Nothing sent. Open Work (/work) when you choose. |
Where. Once your chat account is linked, you choose where pointers go:
| Choice | What you get |
|---|---|
| Chat, then email (default once linked) | Pointers go to your direct messages in chat. Email is the fallback when chat can’t reach you. |
| Email only (default until linked) | Pointers go to your email. |
| Chat only | Pointers go to chat. If chat can’t reach you, nothing is sent. |
Only a verified address is mailed; until you verify it the page says so and offers Send the link again. If chat isn’t linked either, the page says that too.
If your organization has connected chat but you haven’t linked, Link my account takes the place of the chat choices. It signs you in with the chat provider and stores your chat user id; the page then reads “Pointers go to your direct messages in chat, where you’re linked as @handle.” Pointers arrive as one direct message listing up to ten items, each with an Open button, and a one-line phone notification.
When chat can’t reach you. With Chat, then email, the pointer goes by email in the same run and the notification log reads “Chat couldn’t reach you, so it went by email.” Colony marks the link as broken and the page says “Your chat link stopped working on <date>, so pointers went by email.” with Link chat again. With Chat only, nothing is sent and the log records that you couldn’t be reached.
Quiet hours. Turn them on and set a from time, a to time and a time zone. Pointers that arrive then wait for the morning, and are sent in one pointer when quiet hours end. A fault goes to the next operator instead of waiting for you.
What reaches you, and why. A derived list of the work you are pointed at: items you steward, faults if you hold the Operations bundle, strategy proposals if you hold the Autonomy bundle, and each report you subscribed to. Nothing in it is a switch; it follows from what you steward and the bundles you hold. For each repository whose default steward you are, a row reads “<repo>‘s work with no steward · you are its default steward” and links to Account › Tenants.
Who is told next. When nobody answers an obligation, Colony tells a new person rather than repeating itself:
- The steward, or with none, the people who worked in the repository in the last 14 days.
- After the patience, the repository’s default stewards, set in Account › Tenants.
- A day later, a per-repository fault in Operations: “An ask went unanswered”.
An unacknowledged fault widens from its operators to administrators after its patience.
The patience is three numbers: an ask (4 hours, built in), a manual block (2 hours) and an unacknowledged fault (30 minutes). Holders of the Operations bundle set them in Operations › Settings, and a repository can override them. The clock starts at the first delivery, so quiet hours and Digest batching don’t spend patience.
Stewardship never moves on a timer; the ladder only widens who knows. Who has been told on the work item lists each step and the next one.
Who is pointed
Section titled “Who is pointed”- Work items: the steward. When no steward Colony can reach, the repository’s recent writers: members with write access to the repository and activity in it within the last 14 days. Administrators are not pointed because they are administrators.
- Faults (
/operations/health): holders of the Operations bundle covering the tenant; if nobody holds it, the administrators covering it. - Strategy proposals (
/autonomy/strategy): holders of the Autonomy bundle covering the tenant. - Reports: the people subscribed to them.
Delivery
Section titled “Delivery”- A person is pointed at most once per obligation.
- Faults ignore Edge and Digest batching and go at the next run in every mode except Off.
- A fault skips an operator in quiet hours and goes to the others; if every operator is quiet it goes to the covering administrators, and failing that is held until quiet hours end.
- Pointers held during quiet hours are sent at the end of quiet hours.
- Reports ignore your mode and quiet hours; a subscription is its own choice.
What the pointer email contains
Section titled “What the pointer email contains”Each waiting item appears as its own block with its substance (a short plain-text summary, such as the question asked or the number of asks that came back) and its own link into Work or Operations. Up to ten blocks are shown, then “and N more in Work”. The footer says why you were sent it, links to /you/notifications, and offers Stop these emails.
Unsubscribing
Section titled “Unsubscribing”Pointer and sealed-report emails carry a one-click List-Unsubscribe header, which mail clients show as an Unsubscribe button, and a Stop these emails link to /unsubscribe. That page changes nothing until you press Stop these emails. For pointers it turns your mode to Off; for a report it removes that one subscription. No sign-in is needed.
Some emails are exempt and carry no unsubscribe: sign-in messages (magic link, password reset, email verification), because you triggered them and opting out would block sign-in or recovery; invitations, which are sent once at a member’s request and expire; and billing notices, which warn of read-only mode and a paused pipeline and must reach the billing contact.
Notification log
Section titled “Notification log”You → Notifications → Notification log (/you/notifications/log) is a history of the pointers we sent you in the current organization, newest first. Each entry shows the time, the title, the repository and kind, the channel and one sentence saying how the pointer reached you, or why none was sent. Faults, strategy proposals and sealed-report emails appear too. Search with “Was I told about…?” by title, owner/repo, or the item number (?q=). It answers was I told?.
It is a record, not a queue. It has no actions, no read or unread state and no counts, and nothing in it can be cleared or dismissed. To check one item, open /you/notifications/log?repo=owner/name&issue=123; if nothing was recorded, the page says so.
| Method | Endpoint | Auth requirement |
|---|---|---|
GET | /api/account/profile | Any authenticated session |
PUT | /api/account/profile | Authenticated session with verified email |
GET | /api/account/notification-log | Any authenticated session |
GET /api/account/profile returns the current user’s profile including display name, email, avatar URL, email verification status, and notification preferences. Any authenticated session can read this endpoint.
PUT /api/account/profile accepts any combination of displayName, notificationPrefs, and email fields. notificationPrefs is { mode, digestCadence?, quietHours?, where? }, where quietHours is { enabled, start, end, timeZone } and mode is live, edge, digest or off, and where is chat-then-email, email or chat (unset, it reads as chat-then-email once you’re linked and email until then). digestCadence (hourly or daily) is required for digest and refused for any other mode. A save replaces the stored preference, so send the current where along with the rest to keep it. Saving requires a verified email address.
Password
Section titled “Password”Open You → Sign-in (/you/sign-in) to change your account password.
Fields
Section titled “Fields”| Field | Required | Constraints | Description |
|---|---|---|---|
| Current Password | Yes | — | Your existing password. Required to authorize the change. |
| New Password | Yes | Min 12 characters; at least 2 character types (uppercase, lowercase, number, or symbol) | The new password to set on your account. |
| Confirm New Password | Yes | Must match New Password | Confirmation entry to prevent typos. |
| Method | Endpoint | Auth requirement |
|---|---|---|
PUT | /api/account/password | Authenticated session with verified email |
PUT /api/account/password accepts currentPassword and newPassword. The endpoint verifies the current password before applying the change and issues a refreshed session cookie so you remain logged in on the current device. Changing your password also signs out your other sessions, because it advances your session epoch.
Sign out everywhere
Section titled “Sign out everywhere”Sign out everywhere ends every session you hold, on every device, including this one. You sign in again afterward.
It does not change your password and does not revoke your connection (MCP/CLI) tokens.
| Method | Endpoint | Auth requirement |
|---|---|---|
POST | /api/auth/sign-out-everywhere | Any authenticated session |
Unsaved changes
Section titled “Unsaved changes”Navigating away from the Password page with any field filled in prompts the same dialog — “Your unsaved password changes will be lost.” — before discarding your input.
Linked accounts
Section titled “Linked accounts”Open You → Sign-in (/you/sign-in) and find the linked accounts section. The page reads “Sign-in identities linked to your Colony Cloud account.”
Fields
Section titled “Fields”| Column | Description |
|---|---|
| Provider | The provider of the identity: GitHub or Azure DevOps. |
| Account | Your login on that provider. |
| Linked on | The date the identity was linked. |
Empty state
Section titled “Empty state”With no linked identities, the page shows No linked identities yet. and explains that linking a provider identity lets you sign in without a password and lets Colony act on your behalf on that provider.
Connect GitHub
Section titled “Connect GitHub”The empty state has a Connect GitHub button. It starts the GitHub sign-in at /api/auth/oauth/github/login?returnTo=<current path>, where the current path is /you/sign-in, so you come back to this page afterward.
| Method | Endpoint | Auth requirement |
|---|---|---|
GET | /api/account/vcs-connections | Any authenticated session |
GET /api/account/vcs-connections returns the identities listed in the table.
Prerequisites
Section titled “Prerequisites”Navigate to Account → Tenants (/account/tenants). The prerequisites checklist sits below the tenant list; it reads “What you need before connecting a code-host organization.” It is a checklist with no fields to edit. To connect an organization, follow Onboarding.
| Item | What the page says | Link |
|---|---|---|
| GitHub organization admin access | You need admin rights on a GitHub organization to install the Colony GitHub Apps: colony-coder (required) and colony-operations (optional). | GitHub App setup guide |
| Claude provider credential | An Anthropic API key, an Azure Foundry key or an AI gateway token, depending on the Claude provider you choose. Workers use it for every LLM call. | Provider credentials |
| Docker (BYO Workers only) (Optional) | Colony Cloud runs managed Workers for you. You need Docker only to run your own Worker containers. | Workers guide |
| Pipeline Store connection string (Optional) | Only required for Bring Your Own Database mode. Managed mode users can skip this. | Pipeline Store keys |
Each link opens in a new tab.