Salesforce Security Restriction Rules and Scoping Rules

In this Video, I review the 2 new additions to Salesforce Security: Restriction Rules and Scoping Rules. Although similar, the provide different approaches to controlling the records that users can see.
Restriction Rules provide a powerful way to restrict access to records. A Restriction rule can be applied in parallel to existing Sharing Mechanisms.
Scoping Rules provide a "softer" approach to adding some filtering to select List Views and Reports.
I provide explanation and Demo of each.
This video is in the Salesforce Security Spectacular.
Connect with SteveTechArc
Lnk.bio: lnk.bio/steves...
Website: www.stevetecha...
Twitter: / steve_techarc
LinkedIn: / stevesimpson6
#salesforce #architect #security #restriction #scoping
STA 4.14

[@FizzFizzFizzFizzFizz]

Thanks mate!

[@MsMsRaquel]

Very nice! Thank you :)

[@cburt22ify]

Steve, thanks for articulating both of these features in such a concise manner. Im somewhat scratching my head over the need for a Scoping Rule - I am curious as to the driver behind the release of this feature. I just don't seem to grasp the value of having this "soft" restriction to data that a user might literally have access to given an org's sharing model. I have never run into a scenario wherein this might have been helpful solution to a problem my clients have had, have you? For example, whats the point of applying the scope option to a list view when a user could simply navigate to the 'All' list view and access the records they have a share record on?