Admin HQ Compliance includes Consent Logs for internal review of communication consent evidence. Operators can see workspace, lead, channel, consent type, status, and the most recent consent update before investigating message sends.
Open Compliance visibility
From Admin HQ, open Compliance or go to /admin/compliance. The Consent Logs section is an internal operator surface for reviewing communication consent records across workspaces.
Use it for evidence review and troubleshooting. Normal workspace users should update consent from lead workflows, not from Admin HQ.
What the table shows
- Workspace reference for the consent record.
- Lead reference when the consent is tied to a specific customer lead.
- Channel, such as SMS or email.
- Consent type, such as express, implied inquiry, existing business relationship, transactional service message, or unknown.
- Current status, such as active, unsubscribed, or unknown.
- Updated date, which helps show the latest consent proof or unsubscribe change.
Read consent before message events
Consent Logs show the recorded permission state. Message Events show what happened when Cendaro attempted to send or receive a message. Review consent first when a send was blocked, then open Message Events for delivery, failure, or blocked-message evidence.
When to investigate a record
- A contact is unsubscribed but a user expected to send SMS or email.
- A message was blocked because consent was missing for the message purpose.
- A manual lead has unknown consent and needs better proof before marketing outreach.
- A customer replied STOP or START and the workspace needs confirmation that the consent status changed.
- A privacy or support review needs evidence of how consent was captured.
What not to do
Do not treat Admin HQ consent visibility as legal permission by itself. The business workspace is responsible for customer notices, consent, and communication purpose. Admin HQ helps Cendaro verify the record that exists.
Do not paste full customer message bodies or sensitive notes into audit comments. Message bodies belong in Message Events, and audit logs should stay minimal.
Safe operating habits
- 1Confirm the workspace and lead reference before drawing conclusions.
- 2Compare channel, consent type, and status against the intended message purpose.
- 3If status is unsubscribed, treat non-essential SMS or email as blocked.
- 4If consent type is unknown, avoid marketing and review the lead source before service follow-up.
- 5Use Message Events to confirm whether an attempted send was sent, delivered, failed, received, or blocked.
Was this article helpful?
Your answer helps Cendaro improve launch documentation.