Learn MOAR in Winter ’22 with Restriction Rules 🚫 :

Learn MOAR in Winter ’22 with Restriction Rules 🚫
by:
blow post content copied from  Salesforce Admins
click here to view original post


Follow and complete a Learn MOAR Winter ’22 trailmix for admins or developers by October 31 to earn a special community badge and enter for a chance to win one of five $200 USD Salesforce Certification vouchers. Restrictions apply. Learn how to participate and review the Official Rules by visiting the Trailhead Quests page.

Introducing restriction rules

In Winter ’22, we’re bringing you a new way to manage your org’s access control. As admins, you define your organization’s record access through organization-wide defaults, sharing rules, role hierarchy, manual sharing, and other means. Restriction rules are a new tool in your toolbox to manage record access. This easy-to-manage feature lets you pick which users should see which subset of records, allowing you to enhance your org’s security by explicitly defining record access.

How do restriction rules work?

Restriction rules prevent users from accessing records that can contain sensitive data. They also can help users see what they need for their daily work.

With restriction rules, you’ll be able to create a rule and choose which users the rule should apply to. You can also define the rule’s record criteria, specifying which records the users have access to. Read more about restriction rules and specific use cases in the blog here.

How do I create restriction rules?

New in Winter ’22, you can create restriction rules in Object Manager! Previously, you could create restriction rules only through the Tooling or Metadata API. Here’s a restriction rule created using the Object Manager that allows users with the specified profile to see only the task records that they own.

A restriction rules created using the Object Manager.

Enhance your org’s security with restriction rules

If you have users that should only have access to a specific subset of records, restriction rules provide another level of security that you can layer on top of your existing organization-wide defaults, sharing rules, and other settings.

Here are three examples of how using restriction rules can provide an additional layer of security in your org:

Three examples of how using restriction rules can provide an additional layer of security in your org.

Want to learn more about restriction rules? Don’t forget to watch the Winter ’22 Admin Preview on September 10 during Release Readiness Live to see demos of a subset of these new, exciting features. And be sure to check out the Learn MOAR Winter ’22 for Admins Trailmix and follow along on the blog this week for more Learn MOAR!

More Learn MOAR

The post Learn MOAR in Winter ’22 with Restriction Rules 🚫 appeared first on Salesforce Admins.


September 07, 2021 at 09:30PM
Click here for more details...

=============================
The original post is available in Salesforce Admins by
this post has been published as it is through automation. Automation script brings all the top bloggers post under a single umbrella.
The purpose of this blog, Follow the top Salesforce bloggers and collect all blogs in a single place through automation.
============================

Salesforce