SidebarSite navigation.
More
Cert++
Close

Security Exclusion and user access enforcement in trigger handlers

Key Takeaway

Salesforce recommends keeping user access enforcement in triggers instead of adding a Security Exclusion. To fully block a sensitive field, including in reports, use field-level security, not a page layout.

Life Sciences Customer Engagement uses trigger handlers to protect data integrity, record locking, and synchronization. Admins turn these handlers on or off in the "Admin Console". A Security Exclusion lets triggers bypass enforcement of user access permissions. The platform allows it, but Salesforce does not recommend it. If you are considering one, evaluate the decision very carefully before you implement it.

What trigger handlers do

Life Sciences Customer Engagement trigger handlers ensure data integrity, locking, and synchronization. On the desktop site, an admin activates these handlers. Examples include:

  • VisitLockHandler
  • PVLockHandler
  • ContentDocumentLockHandler
  • ContentDocumentLinkLockHandler

If you use the desktop site...

Activate the data-integrity and locking trigger handlers, because activation applies only to the desktop site.

If you use the Life Sciences Cloud app...

The data-integrity and locking functionality is available by default, so you don't need to activate the trigger handlers.

Agentforce Life Sciences Consultant Study Guide

Checklist progress

0/279Learned

Apply security and system configuration fundamentals for Agentforce Life Sciences

0/9

Prepare for the Exam

Play Today's Certle

Study Community

Ask questions and get the latest info from other Agentforce Life Sciences Consultant studiers. 757 members and growing.

Go to Discord