--- title: "Audit Logging" slug: "audit-logging-1" updated: 2026-09-30T18:34:21Z published: 2026-09-30T18:34:21Z canonical: "wiki.cobblestonesoftware.com/audit-logging-1" --- > ## Documentation Index > Fetch the complete documentation index at: https://wiki.cobblestonesoftware.com/llms.txt > Use this file to discover all available pages before exploring further. # Audit Logging **COBBLESTONE SOFTWARE** Contract Insight — User Guide **Audit Logging** *03. Admin User Manual › Searching & Reporting › Audit Logging* **Note:** Each procedure in this guide begins at the Contract Insight homepage, so any section can be followed on its own. Custom fields are configurable, so the exact field list on a contract category record may vary between environments. # 1. Overview There is no single, dedicated "Audit Logging" settings screen in this environment's Administration area or **Application Settings** categories — searching **Application Settings** for logging-related terms surfaces individual, narrower controls instead, such as "**Debug Log for Document Authoring**" (an on/off toggle that records events and errors during the document-merging process) and its paired "**Debug Log History Retention**" setting (in days; 15 in this environment). The practical, general-purpose audit logging mechanism in the live application is the per-record **Audit History** described above: it is always-on, requires no configuration to enable, and automatically records events (views, edits, status changes, and more) against every record as they happen, sourced from both the core application and the Vendor/Client Gateway portal. # 2. Key Elements - No standalone "Audit Logging" configuration screen was found in Administration or **Application Settings** in this environment. - **Application Settings** does include narrower, feature-specific logging controls, such as **Debug Log for Document Authoring** (on/off) and a **Debug Log History Retention** setting (in days, set to 15 here) — these govern diagnostic logging for the document-merge process specifically, not general record auditing. - The general-purpose audit logging behavior in the live application is the always-on, per-record **Audit History** covered under Audit Log — it requires no setup and captures activity automatically as it happens. - This topic is disclosed honestly as partially grounded: it describes what logging-related configuration was and wasn't found, rather than pointing to a single feature literally named "Audit Logging." # 3. Quick Reference Summary [TODO: content needed]