Sea level security.
The next concept that we are going to discuss about this fee level security and it falls under the fee
level access and this is full security more.
The already discussed in detail about the object limit access and the record level access.
And now we are discussing on what fee level access.
So I ask the hierarchy say as you know first comes object level access and there are a user profiles
information sets to determine the object level access.
And once we get access to the object and then comes at record level access yes I have access to this
particular object but does it mean that I have access to all the records.
Definitely not.
It depends on various factors.
And even if I have access to a particular record does it mean that I have access to the full record.
Definitely not mentioned.
It depends on the fee level security so I may have access to the same records you may have access to
the same record but it doesn't necessarily mean that the axis all the feels and that a card that record
access fee level access might be restricted in fact.
This is a very common scenario that we use in real time.
I must say for that we can in fact give like any number of examples for this like the managers in the
business model maybe in such a way that managers only need to access some certain fields or maybe a
particular team of maybe the sales team only should have certain fields only the marketing team should
have access to certain fields.
Like the business model can vary from business to business.
So how do we implement this restriction on fee level.
There comes this concept of fee level security then we can restrict the use us access to view and edit
fields perfect.
Now that we know how to.
Basically what this fee level security.
How do we do that.
There can be confident this fee level security.
We can control the access to fees in two different ways.
One is in page layout the other we have the fee level security settings on a fee.
Using that also began to in page layout in phase layout.
We have two options.
Read only required so for every fee in the page layout settings.
We then either make the field read only or required and then fee level security of a field.
We can make it visible.
I read only however always remember that when there are two places to make a sitting so which one applies.
Say for example in a base layer to the field maybe a required and in the field other settings it may
be read only.
So what happens in the bailout it is required but in the field of security it is read only in those
scenarios.
Always remember that the most restrictive setting applies here the most restrictive setting is indeed
only so the user will have only a read only access
let's have a quick look at how to do these settings.
I have logged into the salesforce developer org and I am in the students object just a bit alone on
a new tech card.
So this is that a card.
This is that a card detail page it did the layout and here we see all the fields out here in the field
properties will be able to set it up so go for any feel you should be able to see these options so we
can make the field either read only or required in a page layout.
This is one off the way we can do field level settings in the labeled level.
And as I mentioned we can also control the field level security using field level security settings
on fields.
So go to the object definition page and go to the custom fields and relationships then you should be
able to see all the fields and go for any field.
You would have the option of set fee love security.
Click on that button and then you should be able to see that option.
You can make the field visible and read only here visible as the name say it will be visible to this
profile and read only as the name says it would be a read only for this particular profile.
So these are the two different ways how we can control field level access to use us and for a particular
field if there are more than one axis defined in each of the way in baseload it is different than in
feel of insecurity for it is different.
Always remember that the most restrictive setting applies and now we know what is field level security
and where do we set it up.
But basically how do we configure this field level security for multiple profiles for configuring this
field level security.
Either we can define the field level security for multiple fields on a single profile or for a single
field on all profiles it depends on how we are basically taking up the task if we are actually making
the field level security for a single profile.
Then we go to that profile and make the changes.
But if we are setting up the field level security for a single field and if we are setting it up for
multiple profiles then we do it a different way.
So when these a profile.
We also mean permission sets because permissions that's basically expand the profile access so in profiles
up mission sets.
So if we want to set up the field level security for multiple feeds for a single profile then we have
to go for profiles and in there we have the feel of the security settings.
We have no navigated to the custom profile sales profile.
And here you see the fee level security.
So now if you want to set up the fee level security for this single profile but on multiple objects
then like we can do it here.
Click on to view one side of the link and here you can edit the feel of the security settings here you
can do the field and security settings for multiple feeds for a single profile.
On the other hand if you want to set it up for a single field on multiple profiles then it is as we
discussed earlier.
Go to the object definition page.
Go for fields and there you'll have that option set fee level security.
Then you can control the fee level security for a single field on multiple profiles.
So basically for testing for us what you can do is that you can update the field level security for
two different users.
In our case we have a system admin and sales profile and maybe here you do not make it visible and then
not log in ask the user to and see if you are able to see that field or not.
So thereby know we have two users so we can not change the profiles accordingly and we can.
That's the scenario.
Perfect.
This is how we assign field level security for different fields on a single profile on for a single
field on different profiles.
Now that is a one other concept that we need to understand that is about a view field access ability
so field level security.
This button we use for setting up the fee level security.
Right.
But this view field accessibility.
This gives us the information about who are on the profiles who can access this particular field and
what does the level of access that they have on this particular field.
So does is the stored and Phyllis name field.
If I click on View accessibility it will list down all the profiles that has access to this particular
field and it will also list down what does the level of access that the profile has on this field.
So it says that this profile has got editable access and why because the field is editable because of
the base layout.
Same and it is hidden field is hidden because of the field level security.
Field is hidden because of the field level security so it also gives the reasoning behind that why this
field is editable why this field is hidden.
Similarly you can access the other fields estimate so all the fees that are there in this object would
appear in this list dropdown list so you can choose the field and you know you can see whether it is
editable or here then and based on which criteria this information is important for the senior admin
for us because while troubleshooting this comes very handy.
Perfect.
So this is all about fee level security and since force.