Understand Bilty audit redaction and evidence boundaries
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
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.
What this guide helps you do
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 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 and open the relevant current record or configuration view.
- Review the displayed state and compare it with the explanation in this guide.
- 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.
- Follow any linked record, status, public evidence, invoice, queue or audit entry rather than inferring that a downstream action happened.
- Use the related guides below for the operational action that changes the record.
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 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.