AWRA OpsHub Search

AWRA Help Center

Copy link
Help Workflow Support
01 Audit Logs Security & Governance 02 Compliance Evidence Packs Security & Governance

Trash & Restore

Deleted records go to Trash rather than disappearing. You can see what a restore or a permanent delete would affect, put a legal hold on anything that must survive, and require approval before anything is destroyed.

Trash is reached from the sidebar. Deleting a customer, item, vendor, asset, user, employee, project, ticket category, expense, budget or custom field definition — twenty-four record types in all — moves it here instead of removing it, which means the everyday mistake — deleting the wrong row — is a two-click recovery rather than a support ticket. Support tickets themselves are closed rather than deleted, so they never come here.

Impact Preview: Look Before You Act

Records are connected, so restoring or destroying one is rarely a single-row decision. The impact preview on a trashed record shows what it is attached to, what would come back with it, what would be affected by a permanent delete, and any blockers standing in the way. Read it before you press anything — especially on a record that carried transactions.

Before every permanent delete, the preview also shows what depends on the record elsewhere: saved reports built on its dataset, active workflows that fire on its events, and ledger lines and journal batches that reference it. Postings stay posted whatever you delete; the preview tells you which ones will point at a record that no longer exists. It is on the web and in the AWRA mobile app.

Legal Holds

A legal hold marks a trashed record as something that must not be destroyed — a dispute, an audit, an investigation. While a hold is active, a permanent delete is refused, not merely discouraged. Holds are placed and released explicitly, and both are recorded.

Retention Policies

A retention policy holds trashed records until a configured date, and blocks permanent deletion until then. Retention and legal holds are separate protections that stack: a permanent delete is refused if either applies, and the screen names which one blocked it. Retention policies are configured under Settings → Security.

Approval Before Destruction

Permanent deletes can require a second person: a request is raised and then approved or rejected. That is the point of the queue — a permanent delete is the one action in the product with no undo, so it is the one worth making someone else agree to.

Every permanent delete asks why, in at least ten characters, on the web and through the API, and the reason is kept with the record’s history. For record types marked high or critical risk, a permanent delete always goes through approval by someone with the approve trash deletes permission, and the approver reads that reason before deciding. The person who asked can neither approve nor carry out their own delete.

Budgets are recoverable too: deleting a spending cap moves it to Trash, and restoring it puts it back, so procurement budget checks and Budget vs Actual read it again from that moment. A permanent delete of a budget is high risk and goes to an approver.

Records Trash Does Not Hold

Some records are never deleted into Trash, because they are cancelled, voided or reversed instead. The Trash page has a section, Recovering records Trash does not hold, with a playbook for each: purchase orders, procurement quotations, sales documents, POS sales, journals, supplier bills, payments and petty cash, saved and scheduled reports, draft emails and messages, and hardware assets in the older register. You only see the playbooks for areas your permissions cover.

Trash Analytics

The Analytics & recovery button on the Trash page opens Trash Analytics: who has deleted what, by module and by record type, what is waiting to be purged, and the approvals in flight, over the last 30 days or any period up to a year. It needs the manage trash permission, and is also in the mobile app.

Everything Is Recorded

Deletion, restoration, holds, approvals and permanent removal all write to the lifecycle ledger, which can be included in an Evidence Pack and cross-checked against Audit Logs. "It was deleted" is answerable with who, when, and under what authority.

Common Questions

  • I restored a record and something is still missing. Check the impact preview — related records may be trashed separately and need restoring too.
  • Permanent delete is blocked. A legal hold or a retention policy is holding it. Release the hold, or wait for the retention date.
  • A deleted document still appears on a report. Historical documents are meant to keep their references; deleting a customer does not rewrite last year's invoices.

Need help with this topic?

Capture the module, record number, branch or warehouse, user, visible message, and what you expected to happen before contacting support.

Open support guide