Skip to main content
Run your business · Command Center
Command Center

Inspect activity

Trace a change back to who made it, what happened, and when.

Updated September 27, 2026 3 min read

A proposal looks different than it did last week, and nobody on your team remembers changing it. Activity at /admin/activity is where you go to answer that question with evidence instead of a guess: who changed a record, what action was recorded, and exactly when it happened.

The Activity screen in the fictional Northline Roofing workspace, showing a recorded history of changes.
Activity in the fictional Northline Roofing workspace. This is the real interface with fictional demo data. Select the image to view it full size.

Finding a change

  1. Narrow the time range

    Set the window to roughly when you think the event occurred; a tight range surfaces the right event faster than scrolling a long list.

  2. Filter it down

    Filter by actor, action, source, or entity type where those filters are available for what you're looking for.

  3. Open the linked record

    Find the matching event and open the record it points to, rather than trusting the event summary alone.

  4. Compare against current state

    Check the recorded action against the record's current state and any related execution or provider receipt to see whether they agree.

For example, if a proposal appears to have changed right after a customer reviewed it, start with that proposal's own events around the time of the review, and keep the proposal's identifier with your findings so a colleague can pull up the exact same record later.

Reading the evidence correctly

An activity event records that something happened inside the application. For anything with an external effect, like a message going out, check the associated result too: an approved request, provider acceptance, and final delivery are three different facts, and an event must be read according to the state it records. Action results walks through the rest.

Events deliberately omit sensitive content, so a row can identify that a message was sent without containing its full body. Open the authorized business record itself for content you're allowed to read.

What to check

  • If you can't find the event you're looking for, double-check the workspace, date range, and filters before assuming it's missing. If it's absent, keep the affected record's ID and approximate time to hand to your technical owner rather than guessing at what happened.
  • Today shows you work to act on; Activity is for investigating what was already recorded, not for finding new work.