-
Notifications
You must be signed in to change notification settings - Fork 33
14) Field Service Lightning
After purchasing Field Service Lightning and enabling it in Salesforce (via Setup -> Field Service Settings), you only need to check the "Service Cloud User" and "Knowledge User" checkboxes on most users that will be accessing your Field Service System. However, there are some exceptions here:
-
Field Service Dispatcher - If a user needs access to the FSL Dispatcher console, they will need to have this permission set license given to them to grant them access.
-
Field Service Scheduling - This allows a user to be shown on the dispatcher console Gantt chart. So if you need a field tech (or someone similar) to show up there, then they will need this license.
-
Field Service Mobile - Any resource that needs access to the special Salesforce Field Service Mobile app will need this license applied to them.
Service Resource - This represents a user or an asset that someone can schedule time with.
Operating Hours - This is kind of a shell/parent object that represents the different operating hours for every region your business operates in around the world. The "Time Slot" object records and "Operating Hours Holiday" records associated with your operating hours record actually represent the hours your business is available.
Time Slots - This is a child record of the operating hours object that represents the times your business is open each day.
Operating Hours Holiday - This is a child record of the operating hours object that represents times and days that your business is not available due to holidays.
Service Territories - These records represent a region/territory, you will associate your operating hours, and each service resource in a territory, to that territory. This ensures that each territory you do business in can only be serviced by service resources in that area, and during time frames appropriate for that area. You can create service territory hierarchies to break larger regions into smaller sub regions.
Service Territory Resource - This object is a junction object between service territory and service resource. It exists because a service resource can work in multiple service territories at once in some instances.