Deleting or restoring a workspace

Workspaces can be deleted safely. Nothing is destroyed immediately. Data is retained and recoverable, so an accidental or unwanted delete can always be undone.

1. 1

   Delete your own workspace

   Owners open Settings ▸ Danger zone ▸ Delete workspace. You are asked to confirm three times: once after reading what deleting means, once by typing the workspace name, and once by typing DELETE. Everyone is then locked out at once, the workspace name and address are freed, and if you are on a paid plan it is set to stop at the end of the period you have already paid for, so you are not charged again. Every record is kept for thirty days so you can change your mind. After that the workspace is permanently erased: every record, every uploaded file and recording, and the sign-ins of anyone whose only workspace this was. That erasure cannot be undone.

2. 2

   Get it back within thirty days

   For thirty days after you delete a workspace it is a change-of-mind window, not a deletion. Every row is kept and a backup snapshot is taken first. The next time you sign in with the same email, the Welcome back screen shows the workspace and lets you REQUEST that we restore it, with a note explaining why; we email you the answer, and you can withdraw the request at any time. A restore brings the workspace back exactly as you left it (its original name too, if nobody has claimed it meanwhile) and stops the erasure clock, though a paid plan you had cancelled may need choosing again. Restoration is reviewed by a person on purpose, because it re-opens billing, seats and data. Platform owners can switch their instance to one-click self-restore from Tenants ▸ Deleted if they prefer. Once the thirty days pass with no restore, the erasure runs and nothing can bring the data back.

3. 3

   Prefer a cooling-off period

   The scheduled path still exists: Settings ▸ Danger zone ▸ Request scheduled deletion emails you a confirmation link, then keeps the workspace working normally for 30 days. Cancel any time in that window; after it, the workspace is archived and the platform operator or your reseller can restore it.

4. 4

   Archive, delete or restore a tenant (platform & reseller)

   Platform owners work from Platform ▸ Tenants, which has dedicated Resellers, Archived and Deleted tabs; resellers open a client under Reseller ▸ Clients. Archive locks members out but keeps the workspace name and domain; Delete (three confirmations, and several at once by ticking them) also frees the name so its owner can sign up fresh. The Deleted tab also holds the restore-request queue: approve to put a workspace back and email its owner, or decline with a reason. Both retain all data, take a backup snapshot first, and are undone with Restore, from the tab, the row menu, or the tenant page.

Erasing a workspace’s data is a separate, deliberate action from deleting the workspace itself, and what it reaches is written down table by table rather than left to a list somebody remembered to add to. Every table that belongs to a workspace is on one of two lists: 300 are erased, and 42 are kept with a recorded reason: our own billing record of what you were invoiced and paid, the workspace itself with its members and plan, the compliance log of the erasure, and settings that hold no content of yours. A table that is on neither list fails our build, so a new feature cannot quietly create somewhere your data survives an erasure.

1. 1

   What the erasure reaches

   All of it: projects, tasks, clients, deals, documents and drive files, invoices and ledgers, calls and their recordings and transcripts, voicemails, meetings and their notes and transcripts, email, chat and direct messages, forms and submissions, everything your AI assistant remembered, the search index built from your content, attendance records, face enrolments and device enrolments, and every connected-service token and API key the workspace held.

2. 2

   What is kept, and why

   The workspace row itself, who is in it and on what plan. Erasing your data is not the same as closing your account. Our invoices to you and the metering behind them, which we are required to keep. The audit record of the erasure. And workspace settings such as your timezone, fiscal year and numbering counters, which contain nothing about your customers and stop invoice numbers being reused.

3. 3

   The backup taken first

   An erasure takes a restore point immediately before it runs, covering 248 of the 331 tables. The 83 it leaves out are deliberate: credentials, connected-service tokens, face enrolments, and high-volume machine-generated records such as the search index and delivery logs. Storing those in a restore point would put live credentials somewhere every owner of the workspace can read them. The restore point records exactly which tables it excluded, so it is never quietly less than it appears.