Organizations and team
Why sites belong to an organization rather than to you, and what that means day to day.
Every site, plan and incident belongs to an organization, never directly to a person. You create one the first time you sign in, and you are its owner.
Using your business name rather than your own is worth the ten seconds — the name appears in emails and is hard to change later.
Why it works this way
- Sites survive people. Someone leaving does not take the monitoring with them.
- The plan has one home. Limits apply to the organization, not per person.
- Access is clean. A site in another organization returns "not found" — not "forbidden" — so ChangeTrace never even confirms it exists.
Roles
| Role | Can do | Also gets |
|---|---|---|
| Owner | Everything | Incident alert emails |
| Member | View the dashboard, add and delete sites | No alert emails |
The alert distinction catches people out. Only owners are emailed about incidents. Email alerts →
Adding people
No invite screen yet
Settings shows your team-member count, but there is no invite UI, and the Free plan is limited to one member regardless.
If you need people added before that ships, ask through Need help?.
Your personal account
Name, email, password, two-factor authentication and connected accounts live in the account modal — user menu → Manage account. That is your login, separate from the organization.
Two-factor is supported, by authenticator app or emailed code.
Multiple organizations
The data model supports it, but there is no switcher in the dashboard, so in practice you work in one. Agencies wanting a client per organization should get in touch before setting that up.
Signing in
Email and password, or Google where enabled. Sign-up needs a 6-digit code emailed to you. Forgotten passwords reset from the sign-in screen.
Authentication is handled by a dedicated provider — ChangeTrace never stores your password.
{ }For developers
Clerk owns all authentication. The API maps a verified session to an internal user and organization; rows are provisioned by a signature-verified Clerk webhook. Organization is the ownership and billing boundary, so dashboard reads are always org-scoped, and the team-member cap is enforced in the webhook by skipping over-cap new members rather than failing the request.