> ## Documentation Index
> Fetch the complete documentation index at: https://docs.marro.si/llms.txt
> Use this file to discover all available pages before exploring further.

# Organisation closure

> Close your organisation, download its data, restore it within 30 days, or hand it to another admin.

Any active **admin** of the organisation can close it while signed in as themselves. The recorded creator is not a separate owner role. Open **Settings → Close organization**, or **Account → Organisation closure** in the app (it opens the same secure web page). Every step asks for your current password. If you sign in with Google or Microsoft, set a password from the sign-in page first.

## Closing

1. Enter your password and choose **Review data**. You see how many leads, contacts, messages, files and other records will be deleted, and you can **Download data** right there.
2. Tick the confirmation and choose **Close organisation**.

Closing signs everyone out at once and stops messages, calls and automations. Your subscription is not cancelled by this, and amounts owed to Marro are not waived.

If records keep arriving while you review (new leads, messages), small changes are fine. If a lot changed, Marro asks you to review again.

## The 30 days

* The closure page shows the exact deadline and how many days are left.
* We email the admin who requested closure 15 days and 1 day before the deadline.
* Until the deadline you can **Download data** or **Restore organisation**.
* After the deadline, restoring is no longer possible. Until deletion actually starts, you can still download your data.

**Restoring** brings everyone back, but new messages, calls and automations stay paused until you choose **Resume activity**. Reminders set before the closure stay cancelled; add new ones where you need them.

**Delete now** skips the rest of the 30 days. It cannot be undone.

## Downloading your data

The download is NDJSON: every record table, the member list and your files (each file in base64 chunks, to be joined in order). A large organisation downloads in several parts, one after another; keep them all. The last part ends with `"completed": true`. Internal AI settlement/provider-pricing records, passwords, tokens and data shared with other organisations are left out. Files over 64 MiB are listed as omitted; [support](https://app.marro.si/legal/support) can send those separately.

## Deletion

After the deadline, records and files are deleted in batches; we aim to finish within seven days. The closure page shows progress for records, files and connected services. Marro keeps its own billing records (contracts, wallet entries, billable AI calls) for eight years, as accounting law requires; they hold no CRM content. Copies outside Marro (phones, downloads you made, other services) and backups that expire on their own schedule are not deleted by Marro.

## Reassigning the recorded creator

The original creator can reassign creator attribution to another active admin under **Organisation creator**, using their password. This does not grant exclusive closure authority: every active organisation admin can close it. The creator record is kept for attribution and account allowances, and cannot change during a closure.

If the recorded creator has left, ask [support](https://app.marro.si/legal/support) for a reviewed reassignment. No creator assignment is needed to let another admin close the organisation.

## In the assistant and WhatsApp

The assistant can tell an admin where a closure stands and open the closure page for them. It never asks for your password and never closes, restores or deletes anything in chat.

## For Marro platform Owners

**Platform → Settings → Organisation closure** has two switches: **Admins can close their organisation** and **Delete data after the 30 days**. Each asks for a confirmation and is recorded in the platform audit log. Both also need their deployment settings (`ORGANIZATION_CLOSURE_ENABLED`, and for deletion `ORGANIZATION_PURGE_ENABLED` and `DELETION_RESTORE_GATE_REVIEWED`) and pass the safety checks shown on that page. Turning them off never reopens a closed organisation; admins keep the 30-day recovery window. An organisation's **Lifecycle** tab shows its owner and lets a platform Owner record or move it, with a reason.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.