Change Data Capture Developer Guide

Change Data Capture
Keep Your External Data Current with Change Data Capture
Change Event Message Structure
Merged Change Events
Other Types of Change Events: Gap and Overflow Events
Subscribe to Change Events
Monitor Change Event Publishing and Delivery Usage
Security Considerations
Required Permissions for Change Events Received by CometD and Pub/Sub API Subscribers
Field-Level Security
Change Events for Encrypted Salesforce Data
Change Event Considerations
Standard Object Notes
Change Events for Fields
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Field-Level Security

Change Data Capture respects your org’s field-level security settings. Delivered events contain only the fields that a subscribed user is allowed to view. Before delivering a change event for an object, the subscribed user’s field permissions are checked. If a subscribed user has no access to a field, the field isn’t included in the change event message that the subscriber receives.

When describing a change event of a Salesforce object, the describe call checks the user’s field-level security settings for that object. The describe call returns only the fields that the user has access to in the describe result of the change event. You can describe a change event through SOAP API or REST API by using the change event name as the sObject name, such as AccountChangeEvent. See describeSObjects() in the SOAP API Developer Guide and sObject Describe in the REST API Developer Guide.

When getting the change event schema corresponding to a Salesforce object, the returned schema includes all object fields, even the fields that the user doesn’t have access to. To get the event schema, use the eventSchema REST API resource. See Platform Event Schema by Event Name and Platform Event Schema by Schema ID in the REST API Developer Guide.