Consent Management for client data use and contact preferences
Key Takeaway
Salesforce recommends building consent management around Data Use Purpose from the start, even if you only manage global consent today, so finer consent later means adding records instead of redesigning. The consent objects store each client's choices, but the firm must build its own process to honor them.
Consent management stores what each client has agreed to: whether they can be contacted, through which channels and addresses, and for what reasons their data can be used. In Agentforce Financial Services, consent management also covers formal consent and disclosure documents, such as annual privacy policies or statements about sharing financial data. For these documents, it records when and how a client agreed. Firms rely on these records to respect client privacy choices and to comply with data privacy laws such as GDPR and CCPA.
The four consent levels
The Salesforce Consent Data Model manages consent on four levels. In order from broad to narrow, the levels are:
- Global consent, stored on the Individual object
- Engagement channel consent, stored in the Contact Point Type Consent object
- Contact point consent, stored in the Contact Point Consent object
- Data use purpose, recorded with the Data Use Purpose object
You can start managing consent at whichever level fits today. You then add finer levels as business needs or regulations change.
Consent in this model follows the person rather than a single address. Any record tied to an individual can have related consent, including leads, users, person accounts, and contacts.