Verify the Bilty tamper-evident compliance chain
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Run the Compliance Centre verifier to confirm the linked SHA-256 event chain and current chain head remain consistent. The guide follows the Help Centre standard: exact route, prerequisites, ordered steps, verification and operational boundaries.
What this guide helps you do
Run the Compliance Centre verifier to confirm the linked SHA-256 event chain and current chain head remain consistent. Bilty Management keeps drafts, issued records, public capability links, finance, integration events and audit evidence as connected but separately verifiable records.
How it works
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
- Go to Bilty Management → Audit / Compliance Centre.
- Confirm the active tenant, intended Bilty record and your permission before entering or changing data.
- Complete the supported workflow: Run the Compliance Centre verifier to confirm the linked SHA-256 event chain and current chain head remain consistent.
- Review the displayed validation, dependent fields and any privacy, finance or integration warning before continuing.
- Save, submit or run the action once and wait for the module response.
- Reopen the relevant register or record and verify the final status, linked records and audit evidence.
Settings to check
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.
Check it worked
Return to Bilty Management → Audit / Compliance Centre 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.
Common mistakes to avoid
- 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.