Consent proof requirements on desktop versus mobile
Key Takeaway
Desktop and mobile consent proof settings are configured separately. A proof method set to Not Required can't be added on that channel, so it can be available on one channel and unavailable on the other.
In Life Sciences Cloud for Customer Engagement, field users record a healthcare professional's (HCP's) consent to a communication subscription. An admin can require reps to add proof of that consent when they capture it. Proof rules are set in two separate places, one for the desktop site and one for the mobile app. The same rep can therefore face different proof requirements depending on where they capture consent.
Where you set proof requirements
A user with the "Life Sciences Commercial Admin" permission sets proof requirements in the Admin Console, on the "Consent Administration" tile. The tile has two sections: "Desktop Site Consent Proof Settings" for the desktop site and "Mobile App Consent Proof Settings" for the mobile app.
The two sections are independent, so a setting in one section has no effect on the other.
You can apply consent settings to the org default or to specific user profiles, using the Admin Console hierarchical settings framework. Different profiles can therefore carry different proof rules.