Audit log page
On this page
Summary
Open Audit Log in your guild's menu to find recorded changes. Choose filters to narrow the events, or follow a history link from another page. Download CSV exports a limited set of matching entries, not the whole log. Start on page 1 when you want the newest matching events.
Which filter should I use?
| Filter | What it selects |
|---|---|
| Min Date / Max Date | When the audit event was recorded, not the raid date or a backdated award date. |
| Character | Events linked to that character. Archived characters are included in the picker. |
| Member | The member whose action produced the event. Archived and banned members remain available in the picker. |
| Raid Group | Events linked to that group, not all events involving its current members. The picker also includes disabled groups. |
| Class | Events linked to characters with that saved class. |
| Loot Type | Events recorded in the selected category. |
| Item Dungeon | Events linked to items with a source in that dungeon. It does not find every raid or change involving that dungeon. |
| Item | Events linked to a specific item. Type a name and select a suggestion to apply it. |
Filters match the event's linked records, not words in its description. A summary can mention several characters or items without linking each one, so a narrow filter can miss that summary.
The dropdown search boxes help find options. There is no general search box for words in audit messages. Simply typing an item name without selecting a suggestion does not apply the item filter.
Does Member mean the person who received loot?
No. Member selects the actor: the person whose action produced the event. To investigate changes to a recipient's character, use Character instead.
For example, if an officer records an award for Sam, Member should be the officer and Character should be Sam's character. Selecting Sam's member account does not find every change made to Sam's records by other people.
Automatic events can begin with System while still being associated with the member who triggered them. For how to interpret messages and related links, see Audit log.
How do the filters combine and reset?
Each selected filter narrows the result further. Changing a selector or date reloads the page and returns to page 1. The filters apply across matching guild history, not only the entries currently visible.
Choose a selector's blank option or clear a date to remove it. When Filter: reset appears, click reset to remove all filters. It is not shown for every combination, including dates alone. Reopening Audit Log from the guild menu also starts with the unfiltered view.
The selected Item can remain active even when its text input is empty after reloading. Check the selected-resource summary above the controls.
How do I filter to a raid or assignment batch?
These filters come from links rather than visible raid or batch pickers. Examples include history on a raid or an assigned-loot batch, and the log opened after submitting loot.
Check the selected-resource summary when arriving through a link. You can add the visible filters to narrow that raid or batch's events further, or use reset to start again.
Raid-group and batch links within an audit entry open the log for that resource. Those links start a new filtered view rather than preserving all your current filters. Character and raid links open their related pages; a timestamp linked to a member opens the actor's profile.
What does Loot Type include?
Choose Prio, Recipe, or Wishlist for events recorded under that category. The received choices are:
- Received (via assign loot page): assignment-category events, including shared batch-detail changes.
- Received (via character loot page): direct received-loot events.
- Received (all): both of those categories.
An award can also cause wishlist or prio updates. Those events keep their Wishlist or Prio category, so Received (all) does not include them. Clear Loot Type when investigating all visible changes linked to a batch.
General settings changes may have no loot type. Any selected Loot Type excludes those untyped events. Selecting a category does not override permission restrictions.
How do the date boundaries work?
Min Date selects events after midnight at the start of its chosen date. An event exactly at that boundary is excluded. Max Date selects events before the chosen day begins, not through its end.
For example, to look through October 7, choose October 8 as Max Date when available. The date pickers stop at today. Leave Max Date blank if you need to include today's events.
The filters compare stored timestamps without converting the entered dates into your browser's local-day boundaries. Widen or clear the range if an event near midnight seems to be missing.
How do I browse older entries?
The normal view shows 50 events per page, newest first. Use the page links below the log to continue; they keep your filters. There are no sortable column headings or column toggles.
An empty result does not prove that nothing happened. Try removing an item, character, or type filter. Some events have fewer related links, and privacy rules can hide others. The audit reference explains those limits.
What do Download CSV and View CSV export?
Download CSV saves a file. View CSV opens the CSV content in a browser view. Both open separately and use your current filters and visibility rules.
The buttons request up to 500 events while keeping the current page number. Since the normal view has 50 events per page, the export is not simply a copy of the entries on screen:
| Current page | Normal view | CSV request |
|---|---|---|
| 1 | Matching rows 1–50 | Matching rows 1–500 |
| 2 | Matching rows 51–100 | Matching rows 501–1,000 |
Return to page 1 before exporting the newest matching entries. A later-page export can be empty even when that normal page has results, because its larger offset is beyond the matching history.
The file includes event descriptions, categories, timestamps, related record IDs, and available names. It does not reveal hidden events, add missing before-and-after values, or provide a complete historical snapshot. For another period, narrow the filters and export again from page 1, remembering the 500-event limit.