# Find out who changed what, and how

> Call `reconstruct_activity` with a record, a person or a time window and you get a plain timeline: who made each change, whether it was a person, an assistant, a scheduled job or an outside service, through which screen or channel, and what changed from and to. On screen, the Activity page shows the same lines under Show plain timeline.

URL: https://biloh.com.au/docs/how-to/find-out-who-changed-what
Category: How-to guides | Audience: operator | Updated: 2026-11-12

**At a glance**

- **Who it's for:** Business owners and the people who run the office
- **Tools it uses:** [`reconstruct_activity`](https://biloh.com.au/connect#reconstruct_activity) · [`get_audit_log`](https://biloh.com.au/connect#get_audit_log) · [`get_audit_log_for_entity`](https://biloh.com.au/connect#get_audit_log_for_entity)

## Ask your assistant

Say what you want to know in plain words: "What happened to this invoice yesterday?", "What did my assistant change this week?", "Who changed this client's payment terms?"

The assistant calls `reconstruct_activity` with one of:

- a record — `entity_type` and `entity_id` (an invoice, a job, a client, a setting);
- a person or an agent — `actor`, which takes a user id (it also matches changes an assistant made for that person), an email or an assistant's name;
- a time window — `from` and `to`.

Each line reads in your business's timezone, for example:

> 10:42 — a team member (finance, in the app) changed due date from 14 Nov to 21 Nov.

An assistant's change names the assistant and the person it worked for, such as "Claude (claude.ai) (assistant, via MCP, for the owner)". A scheduled job, a client in their portal, a subcontractor in theirs and an outside service such as Stripe are each named as what they are.

## Look on screen

Open **Activity** from the menu. Each entry says who made the change and how ("by … (finance, in the app)", "by … (assistant, via MCP, for …)"). Tap **Show plain timeline** to read the same lines `reconstruct_activity` gives.

## Filter the raw rows

When you need counts or a list rather than a story, `get_audit_log` returns the rows and filters on:

| Filter | Example |
|---|---|
| `actor_kind` | `agent` — only changes made by assistants |
| `via` | `contractor_portal` — only changes made in the subcontractor portal |
| `on_behalf_of` | a user id — everything an assistant did for that person |
| `agent_label` | one assistant by name |
| `entity_type` / `entity_id`, `from_date` / `to_date` | narrow to a record or a period |

For one record's full history, `get_audit_log_for_entity` lists every row for it.

## What you will not see

Entries cannot be edited or deleted: not from the app, not by your assistant and not by Biloh's own application code. The change log is append-only in the database itself, which refuses every edit or removal of an entry, whichever app account asks. A correction is recorded as a new entry. The only removal allowed is the scheduled clean-up of entries older than seven years, so every entry is kept for at least seven years. Changes made before the change log started recording the kind of actor show as "not recorded" for that part; nothing older is rewritten.
