Workspace Settings

Workspace Settings is where your organisation's identity lives — its display name, its URL, and who owns it. You'll find it at Settings → Organisation → General.

Adding or removing members and managing invite links is covered on Team management; this page doesn't repeat that.

Name and slug

Two fields, under the Workspace panel:

• Name — the name shown across Pulse. Placeholder Acme Corp.
• Slug — the segment of your workspace's URL, pulse.ciphera.net/<slug>. Changing it changes your organisation's URL. Placeholder acme-corp.

Both are editable by an Owner or an Admin. Anyone else who opens this tab sees the same two fields, disabled. Nothing saves as you type. A save bar appears once a field is dirty, with Save and Discard.

Danger Zone

This section only exists for the organisation's Owner. An Admin can rename the workspace above, but the Danger Zone doesn't render for them at all — not grayed out, just absent. Each row's button reveals an inline confirmation on the same page; neither action opens a separate screen.

Transfer Ownership

Hands the Owner role to another existing member and demotes you to a regular Member. Click Transfer and a picker appears listing every other member who isn't already an Owner — Admins and Members are both eligible, picked by role alone, not seniority. If the organisation has no other members, the panel says so and stops there: "No other members are available. Invite and verify a member first."

Each option in the picker shows the member's email if Pulse has one, or Member <first 8 characters of their id> if it doesn't, alongside their current role. Pick one and click Transfer Ownership (it shows Transferring… while it runs). The server re-checks three things independently of what the picker already filtered for: that you're still the Owner, that your pick is still a member, and that their email is verified — an unverified target is rejected with its own error even though the picker doesn't hide unverified members from the list.

On success you get "Ownership transferred. You are now a member.", your session is refreshed against your new role, and you land back on this same tab, Owner-only rows and all, as a plain Member. A failure shows the server's own message: "Only the organization owner can transfer ownership", "Target user is not a member of this organization", "Target user must have a verified email address", or a generic "Failed to transfer ownership".

Delete Organization

Click Delete and Pulse shows you, in its own words, what you're about to lose:

• All sites and their analytics data
• All team members and pending invitations
• Active subscription will be cancelled
• All notifications and settings

That's the summary. In practice it reaches further than "sites and analytics data" suggests: everything hung off a site — goals, funnels, uptime monitors, annotations, journeys, report schedules — every membership row, every API key the organisation issued, and all org-level notification data. Your live Mollie subscription is cancelled the same moment, and your invoices are anonymised (the personal details scrubbed) rather than deleted outright, kept only for Belgian VAT and legal retention.

Type DELETE, exact case, into the field below the list. Delete Organization stays disabled until the text matches exactly; delete or Delete won't do it. Click it and it runs (Deleting... while it does).

The delete runs in two ordered stages: Pulse cleans up every downstream record first, and the organisation itself is removed only once that entire pass has succeeded. If something goes wrong, the message you get tells you which stage failed, and the two mean different things.

"Organization deletion could not complete — nothing was deleted. Please try again." is the first stage failing. Read it as an instruction rather than as a description of your data: the cleanup works through sites, then notifications, then invoices, keys and memberships, and it stops at the first step that fails, so how much of it had already run depends on where it stopped.

A generic "Failed to delete organization" is the second stage failing, and there the answer is definite: the cleanup finished, so your sites, analytics, memberships, API keys and billing are already gone, and only the organisation record itself is still standing.

Either way, retry until it succeeds, and treat only a success as the end of it. Every step is written to be safe to repeat — a second attempt re-runs the sequence and skips whatever is already done rather than duplicating it — so the retry is what carries a half-finished delete over the line. If it keeps failing, contact support rather than leaving it part-done.

Once it succeeds, you're moved off the organisation you just deleted: if you belong to another one, your session switches to it and you land on its dashboard; if this was your only organisation, you're sent into the workspace-creation wizard instead.

Audit Log

Everything above lives under General. Settings → Organisation → Audit Log is a different kind of page — a running record of what happened across the whole organisation, not the workspace's own settings.

Owner and Admin can open it — a Member can't, the nav item isn't there, and the request behind it is refused the same way. It's a record, not an editor — nothing on this screen can be annotated, exported, or cleared.

Filter by Action (defaulting to All actions) and by a From/To date range; a Clear button appears once either is set. Set the end before the start and Pulse shows a banner instead of quietly handing back nothing: "Start date is after end date."

Each row shows Time, Actor (the member's email, or System when nothing human triggered it, such as an automatic billing-cycle event), and Action as an uppercase badge. The badge turns red only when the action ends in deleted, removed, disconnected, or cancelled — creating something or connecting an integration stays neutral, deliberately not styled as good news. A row with more to say (which site, which plan) expands under a chevron into its own breakdown. Results page 20 at a time, with Previous/Next and a running count of how many you're looking at.

Logged actions span site changes (created, updated, deleted, restored), goals and funnels (created, updated, deleted), Search Console and BunnyCDN (connected, disconnected), team changes (a member invited, removed, or given a different role), the organisation's own settings, and billing (plan changed, checkout started, a subscription cancelled or resumed, and a plan granted on your behalf by Ciphera's team, labelled separately so it doesn't read as something you did yourself). Anything this list doesn't cover still shows — under a plain-language version of its own name rather than a raw code word.

If nothing matches your filters, or nothing has happened at all, the log says so: "No activity yet." The caption underneath explains what will show up once something does: "Workspace actions like site changes and member updates will appear here as they happen."