In this recipe, we are going to take a look at deciding who can use Lightning Experience, how custom profiles are going to be used to get work done, how custom permission sets are going to be used, and how to handle a System Admin, as well as the other standard profiles, using these custom profiles and custom permission sets. We have already understood that all these standard profile users are automatically enabled with Lightning Experience. Let's understand each one in detail. Lightning Experience is not to be given to just one user. We have to understand that we already had another user enabled with Lightning Experience.
- Let's use the
System Adminuser in Chrome, and there is theSample Userin another browser, or an incognito tab in the same browser. If you are using the Lightning Experience, you will see App Launcher. We need to make a custom profile by disabling theLightning Experience Useroption. - You are in the
System Adminnow. Let's go to either Classic or Lightning Experience. Here, we have selected Lightning Experience:
- In order to do our job, we need to go to the Setup icon. Click on
Setupand a new window will open. From here, you can find profiles, or you can go toADMINISTRATION|Users|Profiles. You will find all the profiles here, and you can clone any of the standard profiles:
- Select
Salesforce Userlicenses standard user cloning, and provide a name; a custom profile is ready available:
- If you scroll down, under
Administrative Permissionsyou will find the custom profile where we have deselected theLightning Experience User.
- Let's test the
Sample User; you can see that thisSample Useris in Salesforce Classic. If a specific user or specific users have to be given Lightning Experience, create a permission set. InSystem Admin, under theADMINISTRATIONsetup, there isPermission Sets.Try to create a new permission set. - Permission set comes under
System|System Permissionsand enablesLightning Experience Usersaving:
The permission set has to be assigned to the user, using the Manage Assignments button. Before that, we will check theSample User. There is no switcher, and they are not in Salesforce Lightning Experience. So, let's assign permissions to the Sample User. Then, once you have done that, let's check it in the Sample User window. The first thing to do is to reload/refresh the window.
Note
The best practice is to log out, and then log in. If you do not get the result, log out, and then log in; that's it.
Now, this user has been granted Lightning Experience and a switch to move to Salesforce Classic (Switch to Salesforce Classic) too. All users can be given that profile and you can simply have a custom profile now that a permission set is not needed either. With permission set, a few users are given. If you want to give all users that profile, simply go to that profile and enable the option, that's all there is to it.
The profile has already been assigned to the user, and they have got Lightning Experience with that profile. System administrators need to use the Lightning report builder; a permission set is included for this too. By default, standard user profiles that use the Lightning Experience report builder are not enabled. Simply have a permission set, enable the option Lightning Console User, and assign that required permission set to that user:
We will see this once again when we deal with Lightning Experience reports and dashboards.
- Once again, create a new permission set, go to
Permission Sets|Newand provide a name, then go toReport Builder (Lightning Experience), and clickSave. When we discuss Lightning reports and dashboards, we will look at an example of a standard profile, how to handle system administrators, as well as the standard profile users to give that enhanced report builder.
Now, as you can see, System Admin has got the Switch to Salesforce Classic switcher. This should not be there; it should only be in Salesforce Lightning. We will go to the profile that has been assigned to these users. You have one option, Hide Option to Switch to Salesforce Classic. Because this was disabled, theSystem Adminis able to see that switcher. We will now not enable it, so that they don't see the Switch to Salesforce Classic option:
After doing that, click on Save. This custom property is already assigned to the System Admin user, and we will see the effect now. Now, if the System Admin reloads the page, there will not be a Switch to Salesforce Classic link on the username button (System Admin). We have now gone through all the examples. In the next recipe, we will look at the rollout plan.