Big objects, custom settings and external object access
Secure data that the sharing model doesn't reach: big objects (object and field permissions only), custom settings and custom metadata types (Schema Settings restrictions, protected visibility, where secrets belong), external objects (Salesforce Connect identity types) and Apex controllers that can expose data unless they set an explicit access mode.
Given a scenario, determine the appropriate access control needed to grant access to data that is not standard or custom objects.
~8 min read · 9 practice questions ·
What the exam expects
- Secure a custom big object with object and field permissions, knowing which sharing and automation features it lacks.
- Grant read access to one custom setting or one custom metadata type without Customize Application, and know what Restrict access does.
- Decide where secrets belong: protected settings or metadata in a managed package, otherwise named credentials or encrypted fields.
- Choose the Salesforce Connect identity type that makes the external system enforce each user's own entitlements.
- Recognise Apex controllers that can expose data, and the explicit access modes that close the gap.
Key terms: big object (horizontally scalable store for billions of rows); Restrict access to custom settings (Schema Settings preference requiring explicit Read grants); protected visibility (readable only by its managed package's code); identity type (whose credentials reach the external system); access mode (user or system enforcement of permissions on a database operation).
Key facts
- Detail
- Object and field permissions only; no sharing rules
- Detail
- Restricted until permission set or profile grants it
- Detail
- Custom Lightning and Visualforce components only
- Detail
- SOQL, Bulk, Chatter, SOAP; not REST
- Detail
- On by default; grant Read explicitly
- Detail
- Custom Setting Definitions permission
- Detail
- View All Custom Settings
- Detail
- Behaves like public
- Detail
- Enabled Custom Metadata Types list
- Detail
- Queries use the current user's credentials
- Detail
- User mode from API 67.0; system mode in 66.0 and earlier
Sources for this section (8)
- Big Objectsdeveloper.salesforce.com (opens in a new tab)
- Define and Deploydeveloper.salesforce.com (opens in a new tab)
- Big Objects Best Practicesdeveloper.salesforce.com (opens in a new tab)
- Custom Settings Protectionhelp.salesforce.com (opens in a new tab)
- Read Access to All Custom Settingshelp.salesforce.com (opens in a new tab)
- Read Access to Custom Metadata Typeshelp.salesforce.com (opens in a new tab)
- IdentityType Enumdeveloper.salesforce.com (opens in a new tab)
- Release Note: User Mode by Defaulthelp.salesforce.com (opens in a new tab)
- Why can't an admin hide individual big object rows with sharing?
- When does a user without access to a custom setting see blank values?
- Why does a protected custom setting fail to hide a token in an unmanaged package?
- Which credentials does a per-user external data source use for schema sync?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Platform Sharing and Visibility Architect pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 21 lessons of the Platform Sharing and Visibility Architect guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (9 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams