Read the activity log
Find recorded actions, distinguish a person's work from a background task, and understand access and retention limits.
Admins use Settings → Activity for firm-level actions and the company's Activity page for its permitted company history. The log records actions such as configuration changes and workflow decisions; it is not another transaction ledger.
Find an action
- Open the relevant firm or company Activity page as an admin.
- Use the available search and filters to narrow the action or time.
- Inspect the named actor, action, focus, and timestamp.
- Use the offered export when you need a copy of the visible results.
Company access still applies. A private company's history is not available simply because the viewer is an admin elsewhere in the firm.
Who acted
The log distinguishes a person's attributed action from background or direct operational activity. A workflow started by a person can continue as a task while retaining that initiating person's attribution where the workflow records it.
Do not assume a bill becoming active proves that a named human reviewed it. The learning system preserves the basis it observed rather than inventing a reviewer identity.
Board exports and hidden companies
Some firm-level export actions deliberately record the selected view without company names or row counts. That avoids revealing the existence of an owner-private company to another admin. The absence of a count is not an export failure.
What the log cannot prove
The log is append-only, but it is not a full before-and-after copy of everything in Juan or a record of every browser click. A read, an external action performed directly in Juan, or an old action before instrumentation may not appear as a matching Mendiola write.
Use the linked file, report, or period together with its history when investigating. Share the relevant reference and action time with the operator, without including API keys or private client data in a public support channel.