Organizations Are Here — PulseWatch Works as a Team Now

So today we're shipping organizations. Every account now belongs to at least one, your existing data has been moved into place automatically, and there's a new tab in Settings where you can create workspaces, switch between them, and manage who is in them.

One Account, Many Workspaces

Sign in and you land in your own personal workspace — named after you, created the moment you log in. No setup wizard, no migration prompt, no "import your project" step. If your account predates this release, a backfill already did the work while the update went out: your monitors, status pages, incidents and maintenance windows now belong to your personal organization.

Want more than one? Settings → Organizations has a create form. A name is enough — we generate the slug, make you the owner, and drop the new org straight into your switcher. You can hop between workspaces any time, and the active one is remembered on your account.

Roles That Actually Mean Something

Membership isn't a decorative label. Owners and admins run the org: they can add people by email and remove them, and the backend enforces it regardless of what the UI shows. Members belong to the workspace and see it in their list, without membership controls. And you cannot remove yourself — which saves everyone the awkward "wait, who owns this now?" conversation.

A Paper Trail Instead of a Vibe

Every team tool eventually runs into the same question: "who changed that, and when?" So Settings has a second new tab — Audit. It lists recent events with who did it, what they did, the detail, the IP it came from, and when, newest first. Empty org? Empty state, no fake rows.

Events are written after the change actually succeeds — authentication, CRUD, role changes, billing, account deletion — so the log reflects what happened rather than what was attempted. No more guessing whether that config change went through.

Under the Hood

The schema work is deliberately boring, which is exactly how we like it: two new tables (organization and org_member), an org_id column on monitors, status pages, incidents and maintenance, and one remembered active-org column on the user. All of it applied through the same migration path as everything else in PulseWatch.

Full List — Everything That Shipped

The complete list for this release:

• New Organizations data layer — organization and org_member tables with unique memberships.
• New Personal workspace for every account, created automatically on sign-in.
• New Backfill for existing accounts — personal org, owner membership, active org and resource tagging, idempotently.
• New Create and switch organizations from Settings → Organizations.
• New Add members by email with owner, admin and member roles — enforced on the backend.
• Improvement org_id columns on monitors, status pages, incidents and maintenance, ready for org-scoped views.
• New Settings → Audit — recent events with user, action, detail, IP and timestamp.
• Improvement Fail-open provisioning: org setup can never break sign-in.

Live in Your Settings

Organizations and the audit trail are live on production now — refresh Settings and you'll find both tabs waiting, with your personal workspace already populated. No update required on your end; it all shipped server-side.

Sharing the load is the whole point of a monitoring tool: one team, one place to look, and a log that says who did what. This is the foundation, and it's in your hands today.

— The PulseWatch Team