Profiles in the previous session we discussed about the various levels of access that we have and sales
force starting from object level access to record level access fee level access.
So now that we have an overall understanding about the stands for security model it's time for us to
jump into each one of them and understand what does that in this way do.
Let's understand more about the first object level access especially profiles.
So what does a profile profile basically define how users access objects and the data.
And what does all that they can do within the application as simple as that.
What does that the user can access and what does that a user can do when they log into the application
so as a user when they log into the application.
What does all that I see what all the tabs that I see and what all the tabs that I see here.
What are all the objects that I can access and then we see objects what all that according context within
the objects that I can access everything is defined in a profile.
Similarly what are all the apps that I have here and visual on the apps that I can access.
And is there any restrictions on the logging hours.
Is there any restrictions on the log in IP ranges.
What are the apex glass that I can access.
What was the visual force pages that I can see so all these are defined in profiles so profiles provide
the baseline access that is nothing that can provide more access then profiles
and in that for a user in Salesforce Every user is associated global fight and every use that is associated
to only one profile.
User can have multiple profiles assigned to them they can have will leave one profile assigned to them
and like the other competence in Salesforce we have both standard profiles and custom profiles.
So standard profiles means the profiles which exist by default and custom profiles are created by yes
as the name sees.
Now let's go to the UI and have a look at the profiles.
Go to setup look for profiles
we have managed users profiles so these are all the standard profiles that is provided by Salesforce
by default.
And here we have this option of creating new profiles.
And when we create new profiles we create new custom profiles and we should also understand them to
use standard profiles and then to use custom profiles.
So standard profiles they use then then of requirement matches with a standard profile.
This say a system administrator profile is a generally standard and we do not embedded in any way say
for example does identity use it.
This is a standard use a standard profile
and for this profile as you can see the page layouts are defined the field level security is defined.
The tab settings that are card settings that are defined the administrative permissions what are all
the objects that the user can access.
Everything is already predefined and the number requirement matches with this profile.
We use the standard profile.
If not then we create a new custom profile.
And in real time creating custom profiles are pretty common.
We do create custom profiles in every sense for ZOG.
Now let's take a look at the standard profile that does this sys admin profile so all system administrators
will have this particular profile system administrator profile.
So as you can see here profiling basically controls all these.
It controls which at all the console settings that we have which are all delayed until layouts that
we can access virtually all the page layouts that we can access.
What does the field level security that we have the custom app settings.
Basically we should all the apps that we can access tab settings.
And what does the level of access that we have for tabs default on default off our tab.
Hidden the right guard type settings.
What does a default rate card type for a profile the administrative permissions the various administrative
permissions that we have and the various general use it permissions that we have and the standard object
permissions.
So when coming to standard object permissions it lists down all the objects both the standard objects
and the custom objects here.
And what is the level of you access a particular use that has on the objects.
So this is very commonly called as the correct permissions crowd see are you.
That is create the read a bit and delete the basic correct permissions.
Being a sys admin sys admin has guard access all access basically to all the objects both the standard
and custom objects.
However when creating custom profiles based on the requirement we can modify it accordingly.
Say for example marketing user need to have access to certain set of objects sales tools that need to
have access to a set of objects the same set up maybe do a different set of objects.
And even to the objects different users will have different permissions.
Some users can only read the records.
Some user can read and create records.
Some user can should also be given permissions to edit and delete the records.
So based on the users based on the profiles the correct permissions also differ.
And that is for the standard objects and this is for the custom objects.
And you can see here these are all the custom objects that we created another app and other settings
as well as the possible password policies and how long it can expire.
The logging hours the logging IP ranges logging hours meaning only specific logging hours the user will
be able to access the application and the logging IP ranges if you want to have any restrictions in
the logging IP ranges we can define it accordingly.
And what about that apex glass we should fill out pages pretty much majority of the components that
we access they are defined in profiles.
So profile defines the baseline access every user has got one single profile assigned to them let's
take a quick look at the users at this being a developer edition ARG we have only two users we can create
a maximum of two users we have not created our second user we just have the default user that we have.
And here in my case I have created one user for myself and as you can see that is only one profile assigned
to me.
So when I hit edit you can see here the profile list system administrator and here we can see that like
we can't abated because there is only one single user and have that has to be a sys admin in the Org
so that is the reason but otherwise then we create a second user we should be able to modify the profile
and we basically want to come here to see that one user can help only one profile assigned to him.
Perfect.
So now that we have Gordon understanding about the the profiles now let's see a quick comparison between
the sales force standard profiles and customer profiles.
And let's also quickly create a custom profile and understand it.
So these are all this sales for standard profiles that we have.
And the one that we just discussed about as a system administrator profile.
Let's consider the any other standard profile say for example the standard user profile.
This is a different standard profile that is available in sales force by default.
And when you try to gauge the standard profile we see that the custom app settings can be modified the
tap settings can be modified.
The administrative permissions not all administrative permissions are present for this user.
We can see that some of the checkboxes many of the check boxes are unchecked
the general use it permissions and even in general user permissions like not all the permissions are
available when we feel permissions are available and at the same time we also do not have access to
modify the standard profile right.
We only have access to modify certain attributes that does that tabs and the apps but otherwise we do
not have access to modify any other attributes build the standard object permissions.
These are all pretty standard and we can't modify that and some of the other session settings and the
password policy settings.
So these are the few attributes that we can modify for the standard profile.
So this applies to pretty much any standard competent and sales force standard competence are generally
not 100 percent editable.
We will be able to edit only few of the attributes of the standard competence so the same thing applies
to standard profiles.
So will I be able to change all the attributes of a standard profile.
Only if you are attributes to begin updated.
So in that scenario then we need a custom profile which is very different from the standard profile
that is already existing in Salesforce.
Then we create a custom profile based on the requirement say for example for this field of education
we have already created some custom objects to learn more about the objects and the applications so
for that we created some custom objects.
So when the sales force or when this is being used in the field of education then maybe we create custom
profiles like for instructor's profile separately for students.
We can create custom profiles like that and in case like if it is a that sales and marketing then we
would create sales profiles we would create marketing profiles we would create separate profiles for
field sales manager and we would we might have separate profiles for sales reps we might have separate
profiles for the marketing team like that based on the industry we create separate profiles for separate
requirements.
So now let's quickly create a custom profile hit the New Profile button and as you can see we can upload
any existing profile.
So let me try to clone the system administrator profile and the profile name you can give it as part
of the requirement.
I have given a desk a sales profile.
Perfect.
So our first customer profile is created that is sales profile.
And it has the same level of access that is base layouts the console settings the field level security
the custom app settings the tab settings the record type settings so all the access all the access that
we have for the standard are for the system administrator we have for this profile aspect.
Basically we go into that profile so now we can edit this profile and we can update the permissions
accordingly.
You can see the custom upsetting stats editable.
The tab settings is editable.
The administrative permissions is entirely editable right.
But this was not the case for standard profiles and standard profiles.
These attributes they're not editable they were all read only the general user permissions the standard
object permissions pretty much busted profiles are 100 percent editable we can modify the permissions
aspect of requirements so just to show you one single example what let me do this I'm just taking off
the permissions that we have for the extracurriculars object and let me know say the profile
and let me also create a new user and assign this custom profile to that use it.
So for creating a new user go to use US sheet then you use a backdoor fill in the details here and while
selecting the profiles I have selected the Sales profile the sales profile as a custom profile that
we just created.
So once you are done giving all that perfect now over use it to list created which is mapped to the
profile the sales profile that is a custom profile.
We just created.
Now let's log into the application using this user to now I have logged into the application as a user
to we can see here.
These are all the standard tabs that are available by default and at this user user tool has got the
customer profile the sales profile that we created and for that profile to understand the difference
what we did was we did not give access to the object extracurriculars for this user so we should not
be able to access the extracurriculars object.
So for that what we can do is click on the tabs
here we go.
We should be able to see all the other custom objects that we created say for example instructors and
students.
These are all the custom objects that we created are right and we should also be able to see
courses that are custom objects departments.
But we are not able to see the object extracurriculars right because we did not provide access to this
profile blacks as the extracurriculars object but do remember that this is only one single attribute
that we modified in a profile profile has got a young number of activities that you can modify which
we discussed initially starting from the base layout the record types the logging hours the IP ranges
the Apex class we shall we shall force pages along with the standard object permissions Custom Object
permissions the administrative permissions.
So if we have any number of attributes that we can control in a profile off that this object is one
of them.
So if we just wanted to see that the friends of creating a custom profile and providing access and reworking
access for a particular component that I just wanted to show you the difference.
That is why we revoke the access for one object that is extracurriculars and then we log in to the application
as that user with a custom bike.
We are not able to access the extracurriculars object because this profile does not have access takes
the extracurricular object and not only does the user all the other users who has the profile custom
profile sales profile that we created all the users who have mapped that profile.
The Lord be able to see the extracurriculars object that is why we say that profile is a defined the
baseline axis profiles define what role the objects and data that the user can access when they log
into the application.