The ruling hierarchy as part of the sensible security model.
The already understood about the profile permission sets which forms are an object of the Lexis and
aren't the recording of Alexis we discussed about all the beauty.
Now let's look ahead and understand about the old hierarchy so rule hierarchy.
I have the name.
He does hierarchy of the various roles that have existing in an organization right.
As simple as that.
So in any ARG you know roles are basically just the corporate titles right.
Also known as the business titans which are generally given to people within a business depending upon
the roles and responsibilities they have.
And it also portrays the various duties that they do within that specific role.
Larger businesses they have more titles like you'll see your CEO and executive directors and all these.
So basically role signifies the corporate title of the business title and it does.
It is very much the duties and the responsibilities that a particular person but flops so role hierarchy
meaning.
Then there are various roles defined in an organization.
We also define that whole hierarchy.
We say that in this role the reports to this particular role and a role be reports rule C and then it
goes on and thus a role.
Hierarchy is very much dependent on the organization and it varies from organization to organization
so force also works using this little hierarchy
let the dog go for roles manage uses huddles set up rules.
So this is the default role hierarchy that we have we never develop Iraq.
In fact this is the default only hierarchy that we have in any or even the production arc.
And then then we will say as we'll see item for our business we basically update this little hierarchy
that that is followed in the company.
So basically here you have see all this is the very generalized to the whole hierarchy that we have
so you can expand all these you have an expand all button so see while he is at the topmost level in
the arc and then CFO seal.
In fact CFO seal as we be they are all in the same level as per the rule hierarchy and here you can
see these they are reportedly SVP sales and marketing director.
Their report will lead the North American sales.
So this is the role hierarchy.
We define all the roles and we define where they fall in the whole hierarchy and for every role we assign
people.
So for sequel when you click on sign here you have the option of assigning uses to that particular title
it all hierarchy.
Every use it in the ARG is assigned the role.
So here I am and use Erekat.
Here we see that all option.
So every use it in the ARG is assigned a role fact sitting on the physical hierarchy is one of the initially
actions that we do when we set up our sales force arc so all the uses will be assigned roles and they
will fall under the huddled hierarchy.
This role hierarchy they play a part in that regard level access instance will set to demand as we already
discussed all the beauty it old hierarchy sharing rules and manual sharing are some of the most important
methods of a record level access and sales force or W2 is the most restrictive setting which can further
opened up by the old hierarchy meaning rule hierarchy comes into picture when we want to furthermore
open up access that is given by order beauty the maximum level of access that all the beauty gifts is
publicly right.
Meaning users can view edit and delete other users at cards.
This is the maximum level of access obviously we need on others our cards.
If the order beauty is setting in itself was public right then obviously there is no point of rule hierarchy
right.
Because already we have full access on those records.
So there is no point of having role hierarchy and the role hierarchy doesn't play a part of the social
hierarchy comes into picture when all the beauty is not giving the maximum level of access then that
is a district axes in all WTO
like say for example if auto beauty is private.
In that case users do not have access to other records.
So in those scenarios we can use it all hierarchy to furthermore expand access to those A and for doing
this go to your travel abroad sharing settings.
We already discussed about organization wide default.
And here you have the option of granting access using hierarchies and you can see that this check boxes
are checked by default for the standard objects and for that custom objects will be editable.
So if the checkbox is checked it means users in rows above you in the hierarchy would be able to see
your records.
So users with higher rules will be able to see the records of users who are in the rules below them
in the hierarchy so high ideals can basically see records of liberals ask them bless that and if there
is the checkbox is unchecked then the access level purely depends on all the beauty and maybe it can
be for them or fixed and expanded by the other means.
So this is the whole concept of whole hierarchy.
So the hierarchy meaning user who is above you in the hierarchy they'll be able to see you right.
So if you want to have that feature then grant access using hierarchies should be enabled consider the
scenario for the stored and custom object the order beauty setting is publicly right.
Meaning users have full access on others records.
In this scenario a little hierarchy doesn't have any part to play.
So even if this box is checked or unchecked it doesn't make any difference.
Because users above you in the hierarchy will anyways have access to your records irrespective of this
however if the scenario is like this stored and object has all the beauty sitting as private meaning
only users.
They have absolutely no access to those records.
In that scenario if this checkbox is check then it means users above you in the hierarchy will be able
to access your records.
So this is the concept of an all hierarchy door to order beauty setting as private which does not grant
access to the records.
It can be expanded by all hierarchies.
So when you select this option of royal hierarchy granting access we get access to those that are guards.
So how do we get access users.
What about the role in the hierarchy.
Get access to those records of users who are below them in the hierarchy this is the main concept about
the role hierarchies on top of it sales force.
Furthermore it gives you control to control the level of access that a user has on three objects contacts
opportunities and cases we can control the level of access that users have for these specific objects.
Maybe because these are the core objects in sales for system since what gives you that option.
So how do we set it up.
Go to the old hierarchy
and here say for example click Edit And this is for the role.
See if so let me remind asses we are not updating any rules as such but in your real time project if
you go to this at all hierarchy you will be able to see the actual laws that are existing in the organization.
So now here I mean I did it.
I do not see any options as such.
Right.
Why.
Because the organization wide default is already giving the maximum level of access for these objects
for a case as it is already publicly rate transfer that is a maximum level of access for opportunity
is public read right.
For context it is controlled by parent meaning the level of security depends on the parent object as
such.
So for other scenario let's consider an opportunity.
It is public record right.
So as I mentioned earlier than the order beauty setting is public rewrite or W2 in itself is giving
the maximum level of access.
So there is no point of creating rule hierarchy settings so that is the reason we are not able to see
any chance settings over there.
So now to understand the concept what I'm going to do this I'm going to obtain the opportunity or the
ability setting to private and let me save
now after sharing recalculation.
The order beauty of opportunity is set to private.
Now let me go back to the same rules see a full and I'm refreshing the screen and now we see these options.
So what are the options that we see uses in this role cannot access opportunities can view all opportunities
can edit all opportunities.
So these are the three options that just given in the whole hierarchy.
No access view only access or edit access previously and a lot a beauty setting was publicly right.
These options were not appearing because already all ability has given the maximum level of access.
No audio beauty setting as private which is the most restrictive.
So now we can use it all hierarchy hierarchical still more expand up the access.
So here we can choose.
View all opportunities or edit opportunities if we choose a view of opportunities it means users who
are hired in the hierarchy have again view opportunities what it in the hierarchy.
Edit meaning they can view and also edit opportunities so these are the options that we have in the
old hierarchy settings no access view only access view line edit access so this is all the same as full
security model works it depends on the access levels that is given to you by profiles but permissions
set by the way WD setting by the rule hierarchy.
Basically the combination of all these finally ends up as a card level access for you and sales force
say for example in profile we have the correct permissions and the order beauty setting is private.
So what are the various options and we have our own hierarchy we'll have all the options because the
order beauty setting is private so all the options will be available to us.
But in case of public rule only the option that is available in the old hierarchy is only view and view
and edit while access is not present here because already order beauty is given public read only access
rule hierarchy can only expand the more access then all the beauty it can never revoke the access that
is already given via portability.
So in order beauty is public read only will have only two options will not have the no access option
and affordability is publicly right then all hierarchy has no significant part because all the beauty
in itself is giving the maximum access.
So that is an role for all had I guess such then you can try to replicate the scenario as well.
I updated the order bloody setting to private and in that case like I'll be able to see a all the three
options.
Now what let me do this.
Let me update you to public read on.
And let me save this calculations are going on.
It's done now.
The order bloody setting is a change to public read only.
Now let me refresh and now we do not have technical access option.
Why.
Because order beauty gives read access to others attack guards so that all hierarchy cannot revoke the
access already given by all ability similarly we can try this for the other objects as.
That is for context in cases so here the in for this scenario profile gives the correct permissions
that does all permissions and order beauty is private.
So you have all the options available for old hierarchy and higher profile gives only the create and
the read permissions and the order beauty is set to private.
The options that are available via rule hierarchy is all the three options are available.
So if we choose to view and edit basically what happens technically means viewing other records and
other records as well.
Right.
But if we choose this view on adoption the little hierarchy provides that option.
And though you choose that option however will not be able to edit others a class because profile doesn't
give the unit access always in a member profile provide some baseline access so that is nothing that
can grant more access than profiles.
So as we do not have any taxes as part of profiles do you select the view and adoption.
Users will not be able to eject others records but here for all correct permissions this will work effect.
And here again we have only the create and the read option and here we have asked public read only we
do not see the full access option and we have a view and duplicity.
So do you select view plus edit as we do not have the added Xs and profiles will still not be able to
edit others at Quartz
and thus the scenario profile provides correct permissions.
Public right.
So in this scenario royal hierarchy has no significant role to play because all body already provides
maximum access.
However this is again a tricky scenario when you do not have.
Edit and delete access and profiles and the audio beauty is public record right.
So what happens is you will not have the edit or delete options though the order beauty settings publicly
right.
Because those options are not available in your profile setting.
This is the overall concept of rolling hierarchy since force.