Leaving With Everything You Brought
Leaving a system is a sequence, not a button. Two clocks run through it — seven days on the export, thirty on the deletion — and doing the steps in the wrong order is how an organization ends up with a deleted workspace and an expired download link.
A three-year water and sanitation programme in Kitui closes on 31 December. The consortium that ran it is folding its records into the lead partner’s systems, and the donor’s grant agreement says the financial records must be kept for seven years after closure. The programme’s AWRA workspace has done its job. Now it has to be left properly: everything taken out, checked, and then removed, in that order.
Our take
Take the copy first, check it, and only then ask for deletion. The export lives seven days, the deletion waits thirty, and the deletion removes the same tables the export copied. Do it the other way round and you are working against both clocks at once. Every step below is already in the product; the only thing missing in most exits is the order.
Step one: people take their own
Before the organization takes everything, each person can take what is theirs. Any user can press Export your data on their account page. It prepares a copy of the data held about that one person, and a download link appears in their notifications, valid for 24 hours. For a programme team about to disperse to other jobs, a week’s notice to do this is a courtesy that costs nothing. It is a different request from the organization export, and it does not need an administrator.
Step two: the organization takes everything
Then someone holding the export permission presses Export everything, confirms their password, and waits for the ZIP to be built in the background. What goes in it, what is deliberately left out and how to read it is set out in full in the copy that leaves without the keys. For an exit, three facts about it matter more than the rest.
- It lives seven days. A finished export is deleted from our servers after a week, so press the button when the person who will download and check it is actually in the office.
- It covers what the deletion covers. The export and the deletion read the same map of your tables. Whatever the purge would remove, the export copied.
- It still works after a deletion is scheduled. Nothing about a pending deletion blocks a fresh export, so a late correction during the grace period can be captured in a second copy.
Check the copy before you rely on it
Open it on the day you download it. Compare the row counts in the manifest with what you expect, look at the missing-files count, and store the archive with its checksums somewhere the lead partner controls. A copy nobody opened is a hope, not a record.
Step three: clear what would block the deletion
Some workspaces lock their audit log for a set number of years so that nobody can shorten it. While that lock is on, the organization cannot be deleted: the deletion screen lists it as a blocker and will not continue. Lifting the lock takes a release request and a seven-day wait. If your workspace has the lock, ask for the release at the same time as the export, not after. Whether the log should be kept longer, outside the system, is a question for the export you have just taken; see the log nobody can shorten alone.
Step four: read the preview, then ask
Only an administrator can ask for the organization to be deleted. The first thing they see is an impact preview: how many users and suppliers the workspace holds, how many business records in each module, how many rows in each table, how many stored files and log entries, and anything that blocks the deletion. The preview is valid for fifteen minutes. To go ahead, the administrator types the organization’s name exactly, and the request is accepted only if it comes back with that same preview attached. Nobody deletes a workspace they have not just looked at.
If the workspace has switched on change reviews for organization deletion, the request then waits for a second member who can approve sensitive changes. For a consortium, that second person is usually from the lead partner, which is the right person to confirm the copy has arrived.
The export is a promise you can check. The deletion is one you cannot, so it waits.
Step five: thirty days, then gone
| When | What happens |
|---|---|
| Day 0 | Deletion scheduled for thirty days ahead; the workspace is marked pending deletion and an email goes out the same day. |
| Each week after | A reminder email, saying when the deletion will run. |
| 3 days before, 1 day before | Two final reminders. Never two emails on consecutive days. |
| Any time before day 30 | The deletion can be cancelled by contacting support. |
| Day 30 | The workspace’s records, files and users are purged. There is no bin behind this step. |
The thirty days are the safety net, not a formality. They are where someone discovers that the donor’s auditor wants one more report, or that a supplier’s final statement was never attached. Use them: the workspace is still there, and if something changes, export again.
An exit you can follow on one screen
Every step above exists today, spread across the account page, the security policy and the deletion dialog. These additions bring the exit together for organizations that do it more than once.
An exit checklist
Personal exports, the organization export, the audit lock and the deletion request on one page, in order, each ticked when it is done.
Read-only for the grace period
A workspace that can still be read and exported during the thirty days, but no longer changed.
A purge confirmation
A signed confirmation, sent when the purge has run, for the donor file or the board minutes.
Questions for the week before you leave
Who will download and open the export?
Watch for
Whoever has time.
What to do
Name them, and press the button on a day they are in.
Is the audit retention lock on?
Watch for
Nobody is sure.
What to do
Check now. Its release takes a week.
Have the team taken their own data?
Watch for
Some have left already.
What to do
Give the rest a date before accounts are closed.
Who confirms the copy arrived?
Watch for
The person deleting.
What to do
Better someone on the receiving side.
What AWRA OpsHub does today
- A personal data export for any user, delivered as a download link valid for 24 hours.
- A full organization export of every table and stored file, kept for seven days, available even after a deletion is scheduled.
- An impact preview before deletion, with counts by module, table and file, and any blockers listed.
- A deletion confirmed by typing the organization’s name, optionally held for a second approver, then scheduled thirty days ahead with reminder emails.
- The audit retention lock blocking deletion until it is released after a seven-day wait.
More we can add to your workspace
- An exit checklist screen that walks the steps in order and records when each was done. Commission it
- A read-only mode for the grace period, so records can be read and exported but not changed. Commission it
- Cancelling a scheduled deletion from the workspace, as well as through support. Commission it
- A signed purge confirmation issued when the deletion has run. Commission it
Where we point you to a specialist
- We will not shorten the thirty-day grace period on request. It is the only time a mistaken deletion can still be undone.
The exit checklist and the purge confirmation are the two most asked for by organizations that run programmes with an end date.
See data export and organization deletion
The four exit requests side by side: the organization export, a person’s export, erasing a person, and deleting the organization.
See the way outFrequently asked questions
Should we export before or after asking for deletion?
Before. The export is kept for seven days and the deletion runs thirty days after it is scheduled. Take the copy, check it, then schedule the deletion. You can still take another export during the thirty days if anything changes.
Who can delete our organization?
An administrator, after reading the impact preview and typing the organization’s name exactly. If your workspace has switched on change reviews for organization deletion, a second member who can approve sensitive changes has to agree first.
Can a scheduled deletion be cancelled?
Yes, at any point during the thirty days, by contacting support. Once the purge has run there is nothing to recover.
Why does the deletion screen say the audit retention lock is on?
A locked audit log cannot be deleted, and deleting the organization would delete it. Release the lock in the security policy first; the release takes effect after a seven-day wait.
Can staff take their own data before the workspace is closed?
Yes. Any user can export the data held about them from their account page. The download link appears in their notifications and is valid for 24 hours.