Skip to main content Back CRM Cloud Mastery Sign up Create account

Security, Sharing & Visibility in Practice

Who the user is, which records they see, and how to prove it — the sharing model taught as a set of deliberate decisions.

  • Intermediate
  • 21 lessons
  • 7 modules
  • English

Designed and created by Salesforce Expert

What you'll learn

  • Separate authentication, permission and record access, and configure each
  • Design an org-wide default and open access deliberately from there
  • Use the tools that subtract access, and know why there are so few
  • Spot where a rollup or a report exposes a number the record hides
  • Demonstrate to an auditor what a given user can and cannot see

Course content

7 sections · 21 lectures · 6 hands-on labs

The wall that did not hold 2 lectures
  1. 1.1 The Number That Was Nine Too High
  2. 1.2 The Four Questions Every Visibility Problem Is Actually Asking, And The Fifth One That Only Ever Subtracts
Who the user is 4 lectures
  1. 2.1 Profiles After Salesforce Stopped Investing In Them, Permission Sets, And What Each One Is Still The Right Home For
  2. 2.2H Hands-On: Build Marchwood's Permission Set Groups, Then Mute The Permission The Group Over-Grants Hands-on
  3. 2.3 Object Permissions, View All And Modify All, And The Two Settings That Quietly Outrank The Entire Sharing Model
  4. 2.4H Hands-On: Field-Level Security On The Reserve Figure, And Three Ways To Prove It Holds Hands-on
Which records 5 lectures
  1. 3.1 Org-wide defaults, and why a model that starts open can never be made safe afterwards
  2. 3.2 The role hierarchy is vertical and Marchwood's problem is horizontal
  3. 3.3H Hands-On: Set the defaults, build the hierarchy, and watch Roz break it in ninety seconds Hands-on
  4. 3.4 Public groups, owner-based rules and criteria-based rules — three ways to open access and one question that picks between them
  5. 3.5H Hands-On: Build the panel wall, then log in as three people and try to get through it Hands-on
The exceptions, and the only tools that subtract 4 lectures
  1. 4.1 Manual sharing, teams and the exception layer: when a rule is the wrong answer because the case is genuinely one case
  2. 4.2H Hands-On: Share one claim with Roz by hand, then decide whether that share should have been a rule Hands-on
  3. 4.3 Restriction rules and scoping rules — one of these takes access away and the other only changes what you see first
  4. 4.4H Hands-On: Make the counter-fraud investigations invisible to everybody outside Wesley's unit Hands-on
Where visibility becomes a number 3 lectures
  1. 5.1 Why two people run the same report and get two different answers
  2. 5.2H Hands-on: folders, running users, dynamic dashboards, and the panel numbers that must not cross the wall
  3. 5.3H Hands-on: files, list views and the other surfaces where access leaks after you thought you were finished
Who else is asking 2 lectures
  1. 6.1 Org security controls, and the non-human users: integrations, automation contexts and agent access
  2. 6.2H Hands-on: give an agent exactly the access it needs, and prove it cannot reach the fraud flag
Proving it 1 lectures
  1. 7.1 The access review you can actually run every quarter, what the exam asks about all of this, and where the architect course starts

Requirements

  • CORE-110 Platform Administrator, or equivalent hands-on experience
  • A free Developer Edition org

Description

Salesforce's sharing model is the part of the platform most often configured by accident. This course separates the two questions that get muddled — who the user is, and which records they can reach — and then works through the only tools that subtract access, the places where visibility silently becomes a number, and who else is asking.

It ends with proving it: showing an auditor, or yourself, that the org does what you think it does. It deepens the Configuration and Setup domain of the Platform Administrator exam and carries no exam of its own.

Who this course is for

  • Administrators who own an org's security, and architects who need the floor before they design on it.

Skills you'll practise

Sharing modelProfiles and permission setsOrg-wide defaultsRole hierarchyField-level securityAudit

Related reading