The danger zone at the bottom of the Integrations tab. Clicking Reset opens a phrase modal requiring PERMANENTLY DELETE to be typed, then a secondary are-you-absolutely-sure warning, then a signature pad where the person types their name and draws a signature to authorise. The server re-validates the phrase and the signature independently of the UI.
Also called: wipe my data · start over · delete all test data · factory reset
- 1Each step gates the next; the API re-validates everything server-side as defence in depth.
- 2Deletion runs in a fixed order that respects foreign-key relationships — restrict children first, then cascade parents, then leaf tables.
- 3The audit log is preserved on purpose as the legal record of who did what.
- 4The CRM connection config is preserved so the connection survives the wipe; disconnecting is a separate action.
- 5Estimating-system data is never touched — the wipe is dashboard-side only.
Onboarding, demos and testing leave a company's account full of records that must go before real work starts, and the alternative was a support request. The preservation choices are stated in the route: the audit log stays as the legal record, the CRM config stays so a reset does not silently sever an integration, and the external estimating data is out of scope entirely.
- Clearing an account required a support request and manual database work.
- A single-confirm destructive action is too easy to trigger by accident.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →