Audit log

Guide: How to use the audit log to investigate changes

Open Guild > Audit Log in the top navigation to see who made recorded changes and when. Filter by member, character, item, or loot assignment to investigate a change. The log helps explain what happened, but it does not record every action or let you restore an old list.

What kinds of changes can I find?

The log includes events for:

• Guild registration, joining, settings, ownership, and integration changes.
• Member and character changes, including character claims, notes, unlock exceptions, and archive actions.
• Adding, removing, changing, or reordering wishlist, received-loot, and recipe entries.
• Setting character prios and changing guild item notes, Priority text, and tiers.
• Assigning loot, removing assigned items from a batch, changing batch details, and automatic wishlist/prio updates after items are assigned.
• Raid-group changes, roster changes, and saved raids, attendance, and log links.
• Individual attendee and reserve additions and removals saved through Create/Edit Raid.

One save may produce several events or just one summary; not every changed field gets its own message.

How do I read an entry?

Read the description together with its timestamp and related links. An event may link to a character, item, member, raid, raid group, or assignment batch. Not every event has all of those links.

The actor is the member whose action produced the event. Some descriptions begin with System because TMB made an automatic change, such as marking a wishlist item received after an item is assigned. Those events can still be associated with the member who started the action.

Character and raid links open their pages. Group and batch links open a filtered audit log. A linked timestamp opens the actor's member profile.

Names in the description were written when the event happened. Names beside it may come from the current record. After a character or raid is renamed, those names can differ.

Which filter should I use?

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 assigned item 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.

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, Audit log on 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 start a new filtered view. They do not keep your other filters.

What does Loot Type include?

Choose Prio, Recipe, Wishlist, or Reserves for events recorded under that category. Reserves includes saved reserve additions and removals, whether entered manually or loaded from Softres.it. 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 assigned item can also cause wishlist or prio updates. Those events keep their Wishlist or Prio category, so Received (all) does not include them. Reserve events are also excluded from Received (all). 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. See Why might an event be missing? for those limits.

What do Download CSV and View CSV export?

1. Set the filters for the events you want.
2. Return to page 1 to start with the newest matching events.
3. Choose Download CSV to save a file, or View CSV to read it in a separate browser view.

Both choices use your filters and visibility permissions.

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:

A later-page export can be empty even when that page has results on screen: the export starts farther into the history, as shown above.

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.

How much detail does a message preserve?

It depends on the change. An item removal may name a list and rank. A reorder may only say that items were reordered, without listing the complete order before and after.

A guild-settings save can have one summary with selected changes attached. A group roster update can report counts without a separate event for every affected character.

Create/Edit Raid records one event for each character added to or removed from the saved attendee list, including the initial attendees when creating a raid. Entries identify the actor, character, and raid. Use the raid's history link and the Character or Member filters to investigate; leave Loot Type blank because these are attendance events.

Changing attendance credit, Excused, notes, or row order alone does not create attendee addition/removal events. Unsaved imports and rejected or rolled-back saves create none.

Saving reserves through Create/Edit Raid keeps the general raid create/update event and also records each net reserve addition or removal. Entries identify the actor, raid, character, and item; descriptions use the names available when saved, with record IDs as a fallback. Add three copies of an item for one character and the log records three additions; remove one copy and it records one removal.

Sorting and database row IDs do not affect this comparison. Replacing a list with the same character/item counts produces no reserve events. Changing the character or item records the corresponding removal and addition. Fetching an import, leaving an unfinished search, or rejecting a save creates no reserve events. These events begin with saves made after this feature is deployed; they do not backfill older changes, retain complete ordered snapshots, or provide automatic restoration.

Claiming an unassigned character records who claimed it and links the event to that character. Each changed row saved on Roster > Edit Characters creates one summary covering its main inputs and Details, including alt status, professions, level, spec label, General Raid Groups, and notes. Some labels are shortened, member or main-group changes can use record IDs, and General Raid Groups changes report membership counts. Changes to notes and Spec Label identify the field without copying its text. Long summaries can list only the changed field names. These summaries do not store a complete copy of the character.

An option mentioned in a message is not always proof that a matching update happened. For example, adding received loot can mention the option to mark wishlists and prios received. Check the separate automatic-update events to see which matches were actually changed.

There is no universal saved snapshot of wishlist order. Use the log to investigate recorded changes, not to reconstruct every previous version or automatically undo a save.

Why might an event be missing?

First check your filters. A summary event may not carry the character or item link you are filtering on, even when the save affected it. Broaden the search if needed.

Visibility rules can also hide events:

• Private wishlist events require permission to view private wishlists. Being able to see your own wishlist does not give an exception in the audit log.
• Private prio events require full prio-viewing permission.
• Limiting ordinary viewers to the first few prios also hides all typed prio events from them. It does not show only the top ranks' audit entries.

These rules apply to typed wishlist and prio events. General settings or member-unlock messages may still be visible. See Guild settings and permissions.

Which actions do not create their own event?

Reading pages, exporting data, changing filters, hiding columns, and pinning editor items do not create dedicated guild audit events.

Loading a CSV, fetching Warcraft Logs attendees, or loading Softres.it reserves into an unsaved form does not record the resulting assigned items, reserves, or raid changes. Those require a save. Disenchant/vendor rows skipped during CSV loading do not become audit records for assigned items.

Other actions appear through their underlying saves. Clearing a wishlist can produce item-removal events rather than one “cleared wishlist” event. A loot import can produce assignment events without naming the addon it came from.