> For the complete documentation index, see [llms.txt](https://docs.welkinhealth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.welkinhealth.com/admin/security/read-or-audit-data.md).

# Data Audit

The Data Audit section in the Admin portal lets administrators view and filter a log of data changes across Welkin environments.

***

## Accessing Data Audit

1. Log in to **Admin**
2. Click **Data Audit** in the left navigation menu

***

## Selecting an Environment

The **Environment** dropdown at the top of the filter panel is required. It is pre-populated with the first environment you have audit data access to. Only environments where audit data access has been enabled for your user account appear in the list.

***

## Filtering the Audit Log

Use the filter panel to narrow results. Available filters:

**Row 1**

| Filter          | Description                                  |
| --------------- | -------------------------------------------- |
| **Environment** | Required. Select the environment to audit.   |
| **Start Date**  | Show events on or after this date.           |
| **End Date**    | Show events on or before this date.          |
| **Actor**       | Filter by the user who performed the action. |
| **Target**      | Filter by the subject of the action.         |
| **Patient ID**  | Filter by patient UUID.                      |

**Row 2**

| Filter            | Description                                                                                                               |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------- |
| **Object Type**   | Filter by entity type (e.g., CDT, PATIENT, ASSESSMENT). Options are populated dynamically based on available event types. |
| **Event Subtype** | Filter by a subtype within the selected Object Type. Available options update when you select an Object Type.             |
| **CDT Name**      | Filter by CDT name. Available only when Object Type is set to **CDT**.                                                    |

Click **Apply** to run the filtered query.

***

## Audited Entity Types

The following entity types are tracked in the Data Audit log:

| Entity Type                    | Tracked Event Subtypes                                                                               |
| ------------------------------ | ---------------------------------------------------------------------------------------------------- |
| **Assessment**                 | Created, In Progress, Submitted, Partially Completed, Completed, Expired                             |
| **Assessment Migration**       | Data migration assessment updated                                                                    |
| **Calendar**                   | Event created, updated, deleted                                                                      |
| **CDT**                        | Created, updated, deleted                                                                            |
| **Communication**              | Unsupported WhatsApp message                                                                         |
| **Communication Data Audit**   | Internal message deleted                                                                             |
| **Fax**                        | Created, updated, sent, delivered, failed, received, reviewed, deleted, file added/deleted, assigned |
| **Invoice**                    | Draft created/updated/deleted, sent, pre-authorized, voided, updated, subscription invoice created   |
| **Patient**                    | Created, updated, deleted, care team updated, POC updated                                            |
| **Patient Program**            | Program/phase created, updated, deleted, started, ended, changed                                     |
| **Payment Audit**              | Pre-authorization created/updated                                                                    |
| **Subscription**               | Invoice creation requested, created, updated, cancelled, suspended                                   |
| **Task**                       | Created, updated, deleted, watcher added/removed, comment added/removed, completed, canceled         |
| **Unrecognized Communication** | Email/SMS/voice call reassigned, restored, deleted, permanently deleted                              |

***

## Navigating Results

The audit log uses **cursor-based pagination** — results are loaded in pages without traditional page numbers.

* **Page size** — use the page size dropdown (bottom-left of results) to control how many rows appear per page
* **Next page** — click the right chevron (›) to advance to the next page
* **Previous page** — click the left chevron (‹) to go back one page
* **First page** — click the double-left chevron («) to return to the first page

Navigation controls appear at both the top and bottom of the results table.

***

## Sorting

Click the **Event Date** column header to toggle between ascending and descending sort order. Changing the sort direction resets to the first page of results.

***

## Include Formation

Toggle **Include Formation** (top of the page) to include or exclude formation-related records from the results.

***

## Refreshing Results

Click the **sync icon** (↻) to reload the current query with the latest data.

***

## Exporting Data

Data auditing is useful for ensuring data integrity, verifying user access, tracking changes to important data, and compliance reporting.

**Note:** Only administrators with audit data access enabled for the relevant environment can view Data Audit logs.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.welkinhealth.com/admin/security/read-or-audit-data.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
