Skip to main content

How to use Salesforce Restriction Rules

About Us
Published by jetbi
05 January 2023
75

Why do we need to use Restriction Rules? Most of all, the use of restriction rules is a great solution to protect, and increase the security of your organization. Controlling user capabilities is the key to a well-protected system and a satisfied customer. Using restriction rules will allow you to control the number of users who can see (or not see!) important data that is stored in your system.

The ability to use this technology has appeared quite recently, and in order to successfully apply it in your work, you need to make sure that you are working with the Lightning Experience, Enterprise, Performance, Unlimited, and Developer versions.

1-restriction-rules

Constraint rules are a kind of help tool for Organization-Wide Sharing Defaults and Sharing Mechanisms. This, in turn, means that this tool allows you to sort the final result, which, in turn, will allow you to determine which records users will see in the end.

User access to data will first be determined by Organization-Wide Sharing Defaults, the hierarchy of roles, sharing settings, and territorial management. The restriction rules will allow us to reduce the amount of information allowed to a specific entry that meets the established criteria.

Restriction rules will allow you to fine-tune the visibility of records after all the previous steps in creating security in your organization have been completed.

 

 How to set up restriction rules?

2-restriction-rules

  1. First, we need to go to the object manager.
  2. Now we should select the object on which we want to create a restriction rule.
  3. In the panel on the right, you need to find the ‘Restriction Rule’ and create a new rule. When filling in all the required fields during the rule creation process, do not forget to select the ‘active’ status for the rule to take effect.

During the configuration process, you can select the necessary users for whom this rule is created. Also, customize the posts that your team can see.

Congratulations! You have created your first restriction rule and now your system has become more secure, and therefore more perfect.


Kiryl Yakovlev
Salesforce Administrator
image
Question to the expert
image

We have available resources to start working on your project within 5 business days

1 UX Designer

image

1 Admin

image

2 QA engineers

image

1 Consultant

image
Related Articles
All articles
image
Is Salesforce Winning the Public Sector Race?
An analysis of Salesforce's rapid expansion into the U.S. public sector, tracing its path from cautious early government licensing deals in the 2010s through the launch of Government Cloud in 2012, its pivotal role in COVID-19 vaccine rollouts, and its 2025–2026 push into military and intelligence work via Agentforce and Missionforce. The piece covers major 2026 contracts — including a $5.6 billion Army deal, a $1.6 billion VA agreement, and Pentagon Impact Level 5 authorization — alongside real-world case studies like California's REAL ID processing and the UK's NHS back-office operations. It also examines the structural obstacles still facing Salesforce and other vendors in government tech: legacy IT systems decades old, outdated federal procurement rules, budget constraints, and organizational caution around AI adoption, plus the competitive pressure from Palantir, Microsoft, and Oracle in the race for public sector AI spending.
28 August 2026
image
Why Your Salesforce Flows Are Agentforce's Biggest Problem
This article argues that the most underestimated risk in Agentforce deployments isn't data quality — it's the automation layer: years of overlapping Flows, Process Builder processes, Apex triggers, and managed package logic that no one has reviewed end-to-end. It explains why AI agents inherit automation complexity without the tribal knowledge human admins carry, why technical debt only becomes visible after an agent hits it in production, and why a clean demo is no indicator of production readiness. The article closes with a concrete, tool-by-tool inventory approach using Flow Trigger Explorer, Salesforce Optimizer, Setup Audit Trail, Apex Debug Logs, Agent Builder, and Health Check — scoped to the specific processes the agent will actually use rather than the whole org.
23 July 2026
image
How to Wire Multiple Salesforce Projects in One Org Without Breaking Everything
This article maps the real integration patterns that emerge when multiple Salesforce projects — both managed packages and unpackaged code — share a single org. It covers four concrete patterns: attaching custom triggers to package-owned objects, calling global members exposed by managed packages, writing directly into another project's objects, and runtime-guarded reads of package data. It then addresses access control for authenticated and guest users, including the Master-Detail wall and the without sharing elevation pattern. The piece closes with eight concrete risks (compile-time dependencies that block uninstall, upgrade coupling, silent cascade failures, access invisible to admins) and six actionable recommendations for keeping cross-project coupling manageable.
08 July 2026