Logging & Diagnostics

Audit what users did, monitor system health and capture errors, with activity, email, SMS and API logs plus traces.

• Status Panel — The at-a-glance view of platform health — component versions, benchmarking and configuration advice — and how to use it as a routine check.
• Activity Log — The record of every change: what was altered, from what to what, by whom, from where — plus the separate log of who has read data.
• Audit Chain — Hash-chained audit entries sealed on a schedule, so that altering or removing history is detectable rather than merely discouraged.
• Logs — What the platform records, where each log actually lives in the Architect Panel, and how to choose the right one for a question.
• Error Logging — Choose where errors are recorded, what is captured with them, and why browser output must never be on in production.
• E-mail Log — Every message the platform sent, what it contained, whether it left, and what to do when it did not.
• SMS Log — Text messages sent, the provider identifiers that let you trace one, and the cost and consent considerations specific to SMS.
• API Client Log — Every API call — which client, what it asked for, what it got back, how long it took and how many rows it returned.
• Stack Trace Capture — The settings that govern how much of a trace is recorded, and how to balance diagnostic value against storage and exposure.