Use the Courier audit trail | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/use-the-courier-audit-trail Publisher: Pixie Technologies LLC Module setup, access and navigation Use the Courier audit trail Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Trace who changed an operational record and what changed. Audience: Courier operations staff; Permission: Courier: View; Module v2.0.0; Where to goAdmin Area → Courier & Logistics → Record detail / relevant register What this guide helps you do Trace who changed an operational record and what changed. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects. Follow these steps - Go to the relevant driver, vehicle, customer, job, delivery note, finance or integration record. - Check its history or audit context. - Match action, entity, record ID, staff identity, before/after values and timestamp. - Use the audit entry together with the source record and any notification or sync log. Fields and options This action uses the values already stored on the selected source record. Review that record before continuing. Rules and limits - Secrets are redacted before audit payloads are stored. - Audit evidence supplements rather than replaces the authoritative operational record. Check it worked - The source record, status/history and any downstream notification, provider, POD or finance record should agree after the action. Security, audit and operational checks - Use the exact record and least-privilege role before changing any state. - Verify the saved record after every action; a browser message alone is not evidence that every downstream step completed. - Use protected document and image routes rather than exposing server filesystem paths. - Keep customer, driver, provider, financial and credential data within the authorised workflow. - For provider, finance, employment, transport and compliance decisions, follow the organisation’s authorised professional process. Do not bypass the code flowDo not force database values, invent a status, mark a job completed without signed POD evidence, or expose encrypted credentials to make a screen appear successful. Related guides Courier and Logistics Management module overview (https://pixiecrm.com/help-centre/courier-and-logistics-management-module-overview)Activate and upgrade the Courier module safely (https://pixiecrm.com/help-centre/activate-and-upgrade-the-courier-module-safely)Assign Courier module staff permissions (https://pixiecrm.com/help-centre/assign-courier-module-staff-permissions)Understand the Courier menu and exact navigation paths (https://pixiecrm.com/help-centre/understand-the-courier-menu-and-exact-navigation-paths)