Data, privacy and security

Record and review contact consent

Record and review contact consent in Pixie CRM: follow the supported route, review important fields and verify the result before moving on.

Pixie CRMTask guideUpdated 2026-10-26

Where to goCustomer or Lead → Consents

Before you startIf the screen or action is missing, ask a Pixie CRM administrator to check your role and whether the relevant module is enabled. Do not work around permissions by using another person’s account.

What this helps you do

This guide shows the supported Pixie CRM route for record and review contact consent, the values worth reviewing and the checks to make after the action.

Follow these steps

Open Customer or Lead → Consents in Pixie CRM.
Start the task from that screen and select the correct customer, record, staff member or configuration context when Pixie CRM asks for one.
Review the controls that matter for this task: Customer or lead contact, Consent purpose, Consent status, Source.
Then check Recorded date. Use verified information and do not fill optional values with placeholders.
Complete Record and review contact consent using the supported action on the screen. If Pixie CRM shows a validation message, correct the underlying value instead of bypassing the control.
Save or submit the change and wait for the success or completed state before navigating away.
Reopen the record, status, activity timeline or resulting document and verify that Pixie CRM recorded the outcome you intended.

Fields and controls to review

Customer or lead contact

Consent purpose

Consent status

Source

Recorded date

Checks before you finish

Use the least destructive action available.
Confirm permission and ownership context.
Preserve audit evidence unless authorised policy says otherwise.
Verify the resulting audit or status record.

Permissions and record safety

Keep the change accountable.Use the least destructive action available, work inside your authorised role and preserve activity or audit evidence. Obtain any required approval before financial, privacy, signature or deletion actions.