REPORTING
Understand workspace analytics and audit history
Use tenant-level usage analytics, operational rates and change history to understand adoption, workload and outcomes.
DIRECT ANSWER
Analytics reports receivables state, active workload, contact coverage, email delivery, replies, promises and administrative activity for the tenant. Audit history records significant actions with actor, record, time and relevant before/after state. Use both together: analytics shows where activity occurs; audit history explains how configuration changed.
Read usage overview
Outstanding and overdue values come from Xero-synced invoices. Paid after chasing began describes timing, not causation. Needs attention measures current operational exceptions.
Interpret operational rates
Customer coverage uses enabled contacts over active contacts. Delivery and reply rates use sent reminders as the denominator. Promise kept rate excludes unresolved active promises.
Investigate with audit history
Filter chronologically, open an event and compare relevant before/after values. System processes are labelled separately from signed-in actors.
- 1Start with the time the state changed.
- 2Identify actor and record.
- 3Inspect before and after values.
- 4Open the current record to verify recovery succeeded.
Common questions
Does paid-after-chasing prove Chasd caused payment?
No. The report explicitly shows timing and does not claim causation.
Can members view analytics?
Yes. Workspace members can view operational analytics; owner/admin authority is still required for tenant configuration changes.