Britixo CRMBritixo CRMEnterprise Help Centre
Ctrl K
Audit and compliance evidence · How-to guide

Understand Bilty audit redaction and evidence boundaries

Understand which operational facts are retained while raw API secrets and raw signature-canvas payloads are excluded or redacted. The guide follows the Help Centre standard: exact route, prerequisites, ordered steps, verification and operational boundaries.

Audience: Administrators and authorised Bilty operations staffPermission: Relevant Bilty Management capabilityModule v1.0.0
Jump to steps
Where to goBilty Management → Audit
Before you startRequired access: Relevant Bilty Management capability. Work on the correct tenant and record. Use least privilege and review any dependency or protected workflow warning before continuing.

What you’ll accomplish

Understand which operational facts are retained while raw API secrets and raw signature-canvas payloads are excluded or redacted. Bilty Management keeps drafts, issued records, public capability links, finance, integration events and audit evidence as connected but separately verifiable records.

How the workflow fits together

Review the human-readable audit log and verify the linked tamper-evident compliance chain. Use the module's current status, permission checks, warnings and linked records to decide the next supported action. Where a downstream invoice, WhatsApp queue item, webhook, PDF, POD record or audit event applies, verify it separately.

Follow these steps

  1. Go to Bilty Management → Audit and open the relevant current record or configuration view.
  2. Review the displayed state and compare it with the explanation in this guide.
  3. Compare the live values with the workflow described in this guide: Understand which operational facts are retained while raw API secrets and raw signature-canvas payloads are excluded or redacted.
  4. Follow any linked record, status, public evidence, invoice, queue or audit entry rather than inferring that a downstream action happened.
  5. Use the related guides below for the operational action that changes the record.

Fields and decisions to review

Audit trailHuman-readable events identify actor, source, entity and summary.
Compliance chainLinked hashes make later evidence tampering detectable.
RedactionSensitive secrets and raw signature payloads are excluded or redacted.
VerificationUse the module chain verifier rather than assuming database presence equals integrity.

Record, audit and evidence checks

Reopen the relevant Bilty record or register and confirm its identifier, current status, related parties, timestamps and connected evidence. Check the audit/compliance, payment, public-link, report, API, webhook or WhatsApp evidence that applies to this workflow rather than relying only on a success alert.

How to confirm it worked

Return to Bilty Management → Audit or the resulting register and verify that the stored state matches the intended action. For any downstream automation, confirm the downstream record or queue/log entry as a separate completion check.

Technical basis for this guidance

This guide was checked against models/Bilty_management_model.php; views/admin/audit.php; install.php. It documents only behaviour exposed or enforced by the supplied module; internal secrets, raw signature payloads and unsupported future workflow assumptions are intentionally excluded.

Controls, checks and common mistakes

  • Work only on the intended tenant and Bilty record.
  • Do not bypass a missing permission, validation blocker or protected status by changing unrelated settings.
  • Verify the stored record, downstream integration state and audit evidence after any material action.
Data and workflow safetyConfirm the exact Bilty, authorised audience and final stored status before issuing, publishing a link, recording payment, changing shipment state or sharing a document.
Browse connected topics:audit and compliance evidencebilty management
Review the Bilty audit trailVerify the Bilty tamper-evident compliance chain