Object permissions and record sharing for consent data
Key Takeaway
When account-to-territory alignment changes, existing Communication Subscription Consent and Communication Subscription Consent Compliance Snapshot records aren't reshared automatically. Run both Consent Management batch jobs, one for each object, to realign their sharing.
Consent that field users capture in Life Sciences Cloud for Customer Engagement is stored across related objects. Examples are Communication Subscription Consent and Communication Subscription Consent Compliance Snapshot, plus contact points and digital signatures. A field user can capture and see that consent only when they have access to those objects and to the account. When a consent record is created, Salesforce automatically shares it with the territories aligned to the account.
Objects behind the Consent page
Field users capture consent on the Consent page in the Life Sciences Cloud for Customer Engagement app. The page doesn't write to just one object. It creates connected records across these objects:
- Communication Subscription
- Engagement Channel Type
- Communication Subscription Channel Type
- Data Use Purpose
- Compliance Statement Definition
- Communication Subscription Consent
- Communication Subscription Consent Compliance Snapshot
- Contact Point Address
- Contact Point Phone
- Contact Point Email
- Contact Point Social
- Digital Signature
A field user needs access to all of them, not only to Communication Subscription Consent. These objects might not be included in a standard permission set. Check field users' object access directly instead of assuming their existing permission sets already cover consent capture.
By API name, the objects that field users need permissions for are:
CommSubscriptionCommSubscriptionChannelTypeCommSubscriptionConsentCommSubConsentCmplSnpshtEngagementChannelTypeDigitalSignatureDataUsePurposeComplianceStatementDefLifeSciMarketableProductLifeSciProductAcctRstrcHealthCareProviderContentDocumentContentVersionContentDocumentLink