How to use the Audit Log

The Audit Log is a running history of changes across your workspace: status changes, approvals, deletions, and more.

• Every entry has an action type: Created, Updated, Deleted, Status changed, Assigned, or Completed.
• Entries cover most record types in BrandOps: Creator, Task, Order, Content, Pipeline item, Campaign, Website, Client, Project, Invoice, Return, Issue, and Subscription.
• Each entry shows who did it (with an avatar and initials) and how long ago it happened, e.g. "3 hours ago."
• The page loads your 100 most recent events by default, newest first, plus a total event count for your organization.

Log entries are written as plain-language sentences, not raw database change records.

• A typical entry reads like "Task 'Pack Diwali orders' created" or "Invoice 'INV-0004' deleted."
• Status changes are described with the actual transition when available, e.g. "Order 'ORD-1042' moved from Packed → Shipped," rather than a generic update message.
• If a record's title isn't available, the entry falls back to "an item" rather than showing a blank.
• A colored badge on each entry matches its action type (green for Created, red for Deleted, and so on) so you can scan the list visually.

Narrow the log down with a text search plus two dropdown filters, all of which combine together.

• The search box matches against both the entry's description and the name of who performed the action.
• Filter by Action to see only one type, such as every Deleted event.
• Filter by Type to see only one record type, such as every Order or every Invoice event.
• A count at the bottom ("Showing X of Y events") confirms how much the current filters have narrowed the list.

Visibility into the Audit Log is broader than some other admin-style pages in BrandOps.

• Any member of your organization can open the Audit Log and see the same full history. There's no role restriction hiding entries from certain team members.
• This is different from pages like Posting Approvals, where the actions themselves (approve/reject) are restricted even though viewing is open to everyone.
• Use it as a shared source of truth when a teammate asks "who changed this" or "when did this happen," without needing to loop in an Admin to check.