In the previous session we discussed about the profiles.
What are profiles.
How do we create profiles.
Why do we actually create profiles.
What is the significance of having profiles on all these.
As a senior admin.
We should explore the concept a little more so now let's discuss about some of the considerations key
considerations that we need to have in mind.
Why do we use profiles so profiles as we know that defines how users access objects and what all they
can do.
They can't do within the application so everything is defined in that profile and we know profiles are
back to users so every user has got a profile tacked to them.
Profiles we have both standard profiles and the custom profiles standard profiles as the name says they
are available by default.
When we produce our sales for CRM there are a good number of standard profiles like about 30 35 standard
profiles available.
Standard profiles like any other standard Salesforce competent.
We cannot create them.
We can modify them.
Yes but then only very very few attributes.
We can modify and we cannot delete standard profiles and on the other hand a custom profiles as the
name says they are custom created.
We can create modify and delete custom profiles and as it is custom profiles they are 100 percent customizable
meaning they are 100 percent.
We can update the attributes we began our attributes meaning in the profiles.
It means of the permissions that are basically given as part of that profile and we can delete custom
profiles.
However we should know that we can delete custom profiles only when there are no users assigned to that
profile.
So remove all the user assignments and then we can delete custom profiles Sullivan standard profiles
are already existing why do we create custom profiles.
If the biggest standard profiles as we know we cannot modify all the attributes of a standard profile
we can what if only some certain attributes.
In that case if we have a requirement and we need to modify the other attribute if we want to grant
more access which is not available in the standard profile then we create our own custom profile based
on our business requirement and creating custom profiles it is a very common scenario in all real time
projects.
We have got custom profiles created and use custom profiles also and here.
There is a tip that as a senior admin we need to know that while creating custom profiles we know that
profiles we cannot create a profile directly we can only clone existing standard profile.
Thereby we can create a new custom profile and creating how to create a custom profile and all these
we already discussed so then we clone standard profile.
Basically we can pick any standard profile that is available and we can go on that standard profile
and we can update the permissions accordingly.
However while choosing the standard profile it is always a better option that we choose a read only
profile because read only profile has got only minimum permissions in that.
So it would be easy for us to modify it.
Basically it makes the job easier.
That's it.
Say for example the sys admin profile that is the standard profile.
However it does garlic all the bar missions so mortifying all the permissions that would make the job
already hard so choose a read only profile and then clone it and then create a custom profile that makes
the work a little easier.
So when they talk about that these standard profiles we know then we produce a sales policy item.
We get standard profiles we have some standard profiles like about 30 that do standard profiles we have
but as a senior admin at least not all we should have a good idea about some of the standard profiles.
These are some of the standard profiles that I have listed which is very commonly used in real time
projects.
So at least about these 19 standard profiles we should have an idea about what it does and where it
applies.
So the standard profile is that we need to have an idea about the sys admin the standard platform user
standard use it partner do as a marketing user contract manager the chapel users to add to target external
user solution manager read only I believe we should have a understanding about that.
These the standard profiles.
So if we go to our application all the profiles it is listed under managed users profiles.
We can see all the profiles here and I can see 37 profiles out here among those a few are custom like
about 44 profiles are custom profiles.
So like what thirty three standard profiles we have.
So at least not all they should have an idea about at least a few of these standard profiles so the
first profile that we are going to discuss about is that system administrator profile so then we created
a developer radiation org automatically user gets created and the log in using that user and that this
user is attached to the sys admin profile because that should be at least one person with a sys admin
right.
So automatically that system administrator profile is tactless and we have been using the system administrator
profile as the name says system administrators have 100 percent access to Salesforce they are allowed
to configure and customize the entire application so every single permission all the access rights are
given to system administrator.
So when we talk about these standard profiles I would highly recommend you to go to each of the profiles
and see what all the various options what are all the various permissions that are given to each profile
just see like what all the apps support missions that they have bad permissions and record types administrative
permissions almost all the permissions that are available for sys admin no take agenda look offered.
I'm gettin high level understanding of the standard profiles
that would be the best way to learn about these standard profiles
the next is the standard platform user so let's go back to profiles and go to the standard platform
use it as the name says it is a platform user and the user license is a star salesforce platform.
Basically these users they are allowed to use all the custom apps that is developed as part of the odd
order that maybe they can also be installed from App Exchange or whatever of it.
These users can access those custom apps and also these users can access the main functionality of duck
salesforce platform that is a standard platform user.
So again as I mentioned take a look at the various permissions that this profile has.
Take a look at all the password policies the logging hours.
The apex glasses which which are all the sections that they have access to which are all the sections
that they do not have access to.
Just take a look at that moving on
standard user.
This is actually a very common standard profile that of use in realtime.
Basically this is standard user uses with this profile they are allowed to create and edit the majority
of my most types of records.
They can run report and that they can view the organizations are set up for campaigns they can view
the campaigns but they cannot the managed campaigns as such.
Similarly for solutions they can create solutions.
However they cannot reveal solutions they can edit.
Plus no court does and they can also overwrite a forecaster.
These are some of the important features of this a standard user and as I mentioned this is a common
profile that we use in real time.
Partner use it.
So far use it as the name says it is the users only love to log in from the partner.
So basically users botnet users access the partner portal and this profile we assign to those part number
of users marketing users as the name says at this profile we are assigned to all the people in the marketing
team and these users manage campaigns.
The import leads and they create letterheads they create Hagerty email email templates are they.
They can manage public documents and they can also update their campaign history.
Basically they can also act as a standard user.
Little more of the marketing of functionalities.
This is again one of the common profiles the standard profiles that we use in real time.
Next is contract manager users with this profile.
They are allowed to create edit basically contracts they work on contracts so they can create contracts
edit contracts activate and approve contracts and they can also delete contracts.
But as long as they are not activated they cannot delete activated contracts but inactivated contracts
they can delete them again.
They can edit the personal code does and they can override for guest.
Next comes the chapter for user on the chart that external user as the name says these are for chatter
users the charge to free users.
They can log into chapter and they can access the standard chart of features like other people profiles
groups files and all and they are available with a chart of for user license but the chat to an external
user.
They can also log into chapter and access groups which they have been invited to also.
However they can invite only they can interact only with the members with those groups.
And for this we need the charter external user license next is the solution manager.
The standard profile and as a name say solution manager.
They work with solutions so users with this profile they can review and publish solutions.
They can also act as a standard user.
They have a pretty similar functionality like the standard user and finally comes a read only user.
This is a read only standard profile is also one of the common profiles that we have in production real
time.
These read only users as a name says that users can only read data they can only view all the records
but they cannot get it.
So these are all some of the very common standard profiles that we use in real time.
So as a senior admin it is highly recommended for us to understand at least a high level understanding
about these profiles.
So the best way to learn about this go to each and every profile and says are and see what all the various
permissions that they have that would be a good learning experience.