> For the complete documentation index, see [llms.txt](https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/reporting/audit-logging-and-activity-history.md).
# Audit Logging and Activity History
Use the **Audit Log** in **Rillet** to maintain a single, comprehensive record of every change made across the platform, capturing who performed each action, when it occurred, and what was updated for both financial data and system-level changes. This delivers the traceability finance teams need for internal review, third-party audits, and compliance requirements.
### Use the Audit Log
Follow these steps to review and export activity from the Audit Log:
1. Click your company logo in the lower-left corner.
2. Select **Organization Settings**.
3. Open **Audit & Compliance** to access the Audit Log.
4. Choose **Period** to set a date range and **Item type** to filter by the kind of record affected, or use the filter icon for additional options such as action type and source.
5. Select **Open Item** next to a row, if available, to go directly to the page where the change was made.
6. Click **Export table** to download the filtered list, or **Export detail** to include every field change for the filtered events.
The Audit Log lists every tracked event for the organization in reverse chronological order, with the most recent events at the top, showing the action taken, the date and time, the affected item, its type, the source of the change, and the user who made it.
### What's Included in Audit Logging
The audit log captures changes made across the platform, grouped into the following categories:
| Category | Examples |
| ------------------------ | --------------------------------------------------------------------------- |
| Accounting records | Journal entries, invoices, bills, credit memos, reimbursements, and charges |
| Period close actions | Close, reopen, and review events |
| Contracts and revenue | Contract and revenue-related records |
| Master data | Customers, vendors, products, accounts, and banks |
| Settings | Accounting settings and custom field updates |
| User and role management | Member lifecycle events and role assignments |
Each logged event includes the user who performed the action and the exact timestamp it occurred, giving teams the detail they need to review changes, investigate questions, and maintain oversight and compliance visibility across Rillet.
### Frequently Asked Questions (FAQ)
Can audit entries be edited or deleted?
No. Audit entries are immutable, no one, including Rillet admins, can edit or delete a logged entry, which supports compliance requirements.
Why isn't Open Item available for every row?
Open Item only appears when the event occurred on a page the current user can access. If the event is not reachable by the user, the option does not display.
Is journal entry audit history included in the Audit Log yet?
Not yet. Journal entry audit history is migrating to the unified Audit Log next and will get its own update once it lands.
### See Also
To learn more about managing access and closing periods in **Rillet**, review these articles:
* [**Manage Access and Roles**](/EjmEP4KZ9BVp9j2ho4Mh/settings-and-config/user-roles-and-permissions-overview/manage-access-and-roles.md)
* [**Close the Books**](/EjmEP4KZ9BVp9j2ho4Mh/general-accounting/close-the-books.md)
* [**Create a Journal Entry**](/EjmEP4KZ9BVp9j2ho4Mh/general-accounting/journal-entries/create-a-journal-entry.md)
---
# 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.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/reporting/audit-logging-and-activity-history.md?ask=&goal=
```
`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.