Security Architecture
The mechanisms that earn trust: making sure data is visible only to the people meant to see it.
Salesforce offers many different security settings — profiles, permission sets, field-level security, sharing rules — and it’s easy to reach for the wrong one. In this series, I walk through what each mechanism does and when to use it, so the choice is deliberate rather than a guess.
Whether you’re locking down a new org or auditing an existing one, the goal is to understand which setting solves which problem.
Salesforce Security Simplified: A Guide to Authentication, Authorization and Record Sharing (4.1) Mastering Salesforce Profiles and Permission Sets: Present and Future (4.2) Salesforce Permission Sets and Permission Set Groups, A Guide and Demo (4.3) Session Activation Required for Permission Sets and Permission Set Groups Explained and Demo (4.4) Salesforce Field Level Security FLS Details and Strategies (4.5) Steve's 20 Ways of Sharing a Record in Salesforce (4.6) Salesforce Sharing: OWD, Ownership, and Role Hierarchy (4.7) Salesforce Criteria Based Sharing Rules and Guest User Sharing Rules (4.8) Salesforce Owner Based Sharing Rules (4.9) Salesforce Sharing Using Enterprise Territory Management (4.10) Salesforce Manual Sharing, Account Team, Opportunity Team, and Case Team (4.11) Salesforce Security Implicit Sharing Explained (4.12) Salesforce Security Programmatic Apex Sharing (4.13) Salesforce Security Restriction Rules and Scoping Rules (4.14) Salesforce Security: Sharing Sets and Share Groups (4.15) Salesforce Security: Apex Sharing on Standard Objects lost on Owner Change (4.16) Salesforce Security Apex Sharing on Account Using Territories as Targets (4.17)
A video loads from YouTube only when you click it.
Related Videos
You may also like some of these other video series that I’ve put together.
