Audit log

Summary

Open Audit Log in your guild's menu to see who made recorded changes and when. Use the filters to find a member, character, item, or assignment. 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 notes, unlock exceptions, and some 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, changing batch details, and automatic wishlist/prio updates after awards.
• Raid-group changes, roster changes, and saved raids, attendance, and log links.

These are event families, not a guarantee that every change has its own detailed message. One save may produce several events, or just one summary.

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 award. Those events can still be associated with the member who started the action.

Some links open the related record; group and batch links can open the audit log filtered to that resource. A timestamp linked to a member opens the actor's 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.

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.

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.

How do I find or export events?

See Audit log page for filters, actor versus recipient, date boundaries, pagination, and CSV instructions.

CSV exports follow your visibility rules and contain a limited set of matching events, not all history or necessarily the rows currently on screen. They do not add missing before-and-after values.

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 or fetching Warcraft Logs attendees into an unsaved form does not record the resulting awards or raid changes. Those require a save. Disenchant/vendor rows skipped during CSV loading do not become audit records for awards.

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.

An absent message alone does not prove that nothing happened. Consider the save behavior, filters, visibility, and level of detail the event records.