All right.
So now that we have have a good understanding about the sharing rules let's have a quick look about
at the various concentrations we need to note while using sharing rules.
We know that sharing rules provide a record level access and sales force and we know that sharing rules.
We have five different types or no based criteria based manual sharing manual user record sharing and
Apex manage sharing and sharing rules actually eventually users sharing rules and on then objects.
All the beauty is either private or public read only then the use sharing rules to furthermore expand
the access for those related object records.
So that does.
That is where exactly sharing wealth comes into picture.
And that is the basic concept of using sharing rules.
And we also know that sharing rules can only open up more access than all beauty but not at restrict
access that is already granted by all beauty and yes the order beauty of that particular object should
be private or public read only only then we'll be able to create sharing rules OK.
This is the case of multiple sharing rules because in object know in real time we create multiple sharing
rules.
So for some set of records through a sharing rule have got to read only access and through another sharing
rule in the same object.
I have got a read write access maybe because I am in different public groups due to some scenarios.
I have gained different access levels from different sharing rules.
So in that scenario what happens in that scenario I get the most permissive access limit meaning the
maximum access limit.
So one sharing rule is giving me a read write access so I'll be able to have the read write access on
those records.
And this is about a related records.
So when we get access to some set of records automatically we are also granted access to its related
records.
Say for example opportunity sharing rules.
There is opportunity shared Roland but that opportunity sharing rule is giving me access to the opportunity
records.
So in that case I also get additional access to its related account.
Similar scenario happens when we create contact sharing rules case sharing rules even in those scenarios
we get access to the related outcomes.
So that's what it means when we have access.
We also get access to its related records
this ESPN radio love it off users in that old hierarchy.
They automatically get access which uses one lawyer and the hierarchy gets say for example.
That is a person who reports to me and he gets access to a sharing rule.
So automatically as I am above him in the rule hierarchy I automatically get access.
And we know that for a standard objects the grand axes using hierarchies is automatically selected and
for custom objects the checkbox is editable so if that option is selected then automatically the person
being live in that old hierarchy if he gets access then automatically I get access
and once we create the sharing rule and once it is done saving then you go edit this sharing rule in
that scenario we can't change the shared with field settings we can quickly see that you never develop
Rod we have already created a lead CHEERING rule and now that I'm editing the rule and now you can see
that this shared with option is not editable.
So you cannot edit this particular field value you can actually add or remove users from that.
This particular group unit sales reps but as such this shared with value is an art.
Edit.
These are actually my new things but important things that a senior admin has to know
and the ones shading rule is created it automatically applies to all the existing cards off that object
and it also applies to all the newly created cards and it applies both to active and inactive users
and then we change the access level for a sharing rule than all the existing cards are automatically
updated meaning this is the sharing really they're talking about and here we have the Axis limit and
once a sharing rule is created and then begin go on added the shading rule at a later point of time.
There does axis level is editable so currently does read right.
If I change it to read only then the related axis for those records also gets changed
and what happens when we the leadership group sharing rules can be deleted as well.
All right.
So when we deleted sharing the sharing or axis created by that tool is also automatically removed.
Say for example that associating rule that give me access to some hundred icon Records.
And if that the sharing rule is deleted then automatically I lose access to all those hundred icon Records
Yeah.
This is a very important concept that is a sharing a re evaluation.
So what is is a shared angry evaluation is a little different from what we are talking about.
We were talking about like what happens when a sharing rule is created and what happens when a sharing
rule is edited.
Right and what does the impact of the records.
What does the level of access that user gets an all these.
But now what we're talking about is a sharing re evaluation meaning a sharing really gets the evaluated.
So under what scenario is that sharing we get to evaluate it whenever we modify use us in the public
group out of rule territory in all those scenarios sharing rules gets reevaluated like for example for
all the beauty we have already seen when we changed the world of beauty setting of a particular object
then we see that a revaluation is happening in this art right.
Similarly for sharing rules also re evaluation happens this error evaluation happens when one of these
changes that takes place and how long the city evaluation takes.
Basically the ZT calculation of this sharing rules can take anywhere between one minute to several hours
so that depends on the are basically the number of users in the ARG.
Basically the customizations that is there in the ARB and also the number of records that is there in
your sales force are based on all these evaluation time it varies.
And while this recalculation runs in the background at that time will not be able to create any new
sharing rules or will not be able to modify any security such as settings as such like updating the
WTO or other security settings.
And while we understand about this the sharing the evaluation we should also know about one important
thing that is called a default sharing calculations.
So what does this default sharing calculations meaning like in real time when we have large number of
records happening say for example the lead object concert the lead object like you have like 3 million
or 4 million lead records and then we make a change or we create a rule that is impacting the leaves
records that is impacting a large number of elite records and that's another definitely the evaluation
is going to take a really long time.
So in that scenario what we can do is we have this option of a default sharing calculations meaning
which can temporarily suspend the automatically calculations that take place and how we can do that.
We can do that by raising a support ticket and basically this a default sharing calculations is a limited
feature and Assad's full support can definitely help you enable that and the ones you have that feature
a name but that then you can temporarily suspend these automatic re calculations and plan those re calculations
to happen during a maintenance phase so that we'll have very less impact on the users.
These options adult we do not use in every project but we do not use in every order.
It is definitely a good to know for senior admins that one such option do exist.
Perfect.
Moving on and basically this is about the transferring records from one user to another so that's an
idea.
Also sharing user reevaluated and in that re-evaluate which can add access also which can remove access
also that this recalculation.
We know that it automatically happens and we know we discussed about individual scenarios that automatically
happens but other than that we can also manually force this evaluation to take place how we can do is
that in our sales files are in the sharing rules V we should have a button that just called us recalculate
so when they hit this button automatically the sharing lose gets recalculated but this button we should
use only in case of troubleshooting.
Ah then the sharing rule is not showing the expected behavior in those scenarios we use this recalculate
button.
So these are some of the important considerations that we need to note while using sharing routes.