| AWRA OpsHub

 Search
Advanced Certificate on pass

Trash, Recovery, and Legal Holds

Control restore, impact preview, force-delete approvals, legal holds, purge windows, and deletion evidence.

3 lessons 45 min 5-question assessment 80% to pass
Take the assessment

What you’ll learn

  • Restore records with dependency awareness
  • Read impact previews before force deletion
  • Use legal holds to protect evidence from purge
  • Preserve proof of purge decisions and approvals

Course content

3 lessons · 45 min of reading
01
Lesson 1 of 3 Reading 13 min

Trash is a recovery layer

Trash gives teams a chance to recover from ordinary deletion mistakes. A deleted record may still matter for stock, finance, audit, compliance, customer history, or linked documents.

Restore should be dependency-aware. A record should not return in a way that breaks references, duplicates active work, or changes a controlled process without review.

In practice, restoring a supplier may require checking linked purchase orders, documents, sync mappings, and inactive status. Recovery is safer when the impact is visible before the button is clicked.

Recovery decision guide

Action Use when Control check
Restore Record was deleted by mistake Review dependencies and active duplicates
Keep trashed Record is obsolete but retention still matters Confirm reporting and audit needs
Legal hold Evidence may be needed for dispute or audit Block purge until hold is released
Force delete Retention allows permanent removal Require impact preview and approval

Key takeaways

  • Trash protects against accidental deletion.
  • Restore should consider linked records and process impact.
  • Recovery can affect finance, stock, audit, and integrations.
  • Impact awareness is safer than blind restore.
02
Lesson 2 of 3 Workshop 16 min

Impact preview and force delete

Impact preview shows what deletion or purge could affect: linked records, documents, audit trail, stock evidence, customer history, finance references, and integration mappings.

Force delete should be rare and approval-controlled. It permanently removes recovery options, so the approver should understand legal, operational, and reporting consequences.

In practice, force deleting an old test customer may be acceptable after impact review, while deleting a customer with invoices, payments, and disputes should be blocked or escalated.

Key takeaways

  • Impact preview explains deletion consequences.
  • Force delete removes recovery options.
  • Approval should be required for high-risk purge actions.
  • Linked finance, stock, and legal records may block deletion.
03
Lesson 3 of 3 Practice 16 min

Legal holds and purge evidence

A legal hold protects records from deletion or purge because they may be needed for dispute, investigation, audit, regulation, or contractual evidence.

Purge should produce evidence: who approved it, when, what scope, why retention allowed it, and whether any holds blocked records. The evidence matters because the deleted data may no longer exist to explain itself.

In practice, if a tenant is under audit, related invoices, documents, logs, suppliers, and approvals may be placed on hold. The purge job should skip held records and report that decision.

Key takeaways

  • Legal holds override ordinary purge timing.
  • Purge decisions should leave approval and scope evidence.
  • Held records should be skipped and reported.
  • Deletion governance protects trust after data is gone.

Finished the material?

Take the 5-question assessment and earn your certificate — 80% to pass.

Take the assessment

More in this path

Workflow Builder Basics

Open course

Approval Workflows

Open course

Security & Data Protection

Open course

Help Center

Need a quick answer while you read?

Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.

Search all approved AWRA public help articles.

Open Help Center