Organizations
How organizations work in SitePulse — personal vs team organizations, switching between organizations, and organization-scoped resources.
Organizations are the top-level container in SitePulse. Projects, audits, billing, and team membership are all organization-scoped — everything you do in SitePulse happens within an organization.
Personal organization
When you register, SitePulse automatically creates a personal organization linked to your account. It behaves exactly like a team organization, but has no other members by default. Your personal org is where solo projects live.
You cannot delete your personal organization — it persists as long as your account exists.
Team organizations
Create additional organizations for client accounts, business units, or project teams. Go to Settings → Organizations → New Organization.
Each team organization has:
- Its own member list (owner, admins, members)
- Its own subscription and billing
- Its own projects and audits
- Its own API key configuration (BYOK)
Switching organizations
The Org Switcher appears in the left sidebar below the SitePulse logo. Each organization in the list is labeled so you can tell them apart at a glance — Personal for your own workspace, Owner for team organizations you created, and Shared · Member (or Admin/Viewer, with a member count) for organizations you were invited into. Two organizations with the same name are no longer ambiguous.
When you switch organizations, the app reloads into the selected organization's dashboard: its projects, audits, and settings replace the previous org's everywhere, and any project you had selected is cleared (project selections don't carry across organizations). Your user account (email, password, notification preferences) persists across orgs.
If you are a member of only one organization, the Org Switcher is hidden.
Organization-scoped resources
The following are organization-scoped (belong to one org, not transferable):
| Resource | Notes |
|---|---|
| Projects | All projects belong to one org |
| Audits | Audits belong to a project, which belongs to an org |
| Billing subscription | One subscription per org |
| CMS integrations | Configured per project (within an org) |
| Team members | Membership and roles per org |
| Brand Voice | Per project, within an org |
| Personas | Per project, within an org |
The following are user-scoped (belong to you, not an org):
| Resource | Notes |
|---|---|
| API keys (BYOK) | Set on your user account, available across all orgs |
| Notification preferences | Per user |
| Google Search Console OAuth | Per project, but the OAuth token is per user |
Leaving an organization
Go to Settings → Organizations → [Org name] → Leave. You cannot leave an organization if you are the only owner. Transfer ownership to another member first, or delete the organization.
Organization deletion
Deleting an organization permanently deletes all projects, audits, and associated data. This action cannot be undone. The subscription is canceled immediately and no refund is issued for unused time.