> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/reporting-and-integrations/reporting/review-deletion-activity.md).

# Review deletion activity

Use **Deletion activity** to see who deleted records, when, and which records were included in each deletion.

> **Where to find it:** Dashboard → Reports → Operations → Deletion activity.

Your role needs reporting access. The report shows only affected records your role can access; restricted invoices, quotes, and inspection reports are omitted when you lack their access permissions.

1. Select a date range.
2. Optionally filter by the person who deleted the records or by record type.
3. Review the affected records. **Direct** identifies the record the user chose to delete; **cascade** identifies records included with their parent.
4. Use **Export CSV** to download the filtered report.

Each row represents one deletion action. Dates use your business timezone. Filtering by record type keeps deletion actions containing that type, so you can still see their other permitted affected records.

The report is an audit trail. It does not open deleted records or restore them. Primary records also have deletion events in the Activity feed.

See [Delete a customer, property, job, quote, or invoice](/customers-and-work/customers/delete-a-record.md) for deletion scope and invoice accounting behavior.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://learn.withessential.com/reporting-and-integrations/reporting/review-deletion-activity.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.