Skedulo uses permission sets to grant users access to Skedulo objects. The Skedulo managed package includes the following permission sets:
"Skedulo Scheduler."
"Skedulo Resource."
"Skedulo Base."
"Skedulo View All."
"Skedulo API User."
"Skedulo Resource Without Assigned Apps."
"Skedulo Community Resource."
These permission sets are added, as required, to the Salesforce user records. It’s important to note that if you use custom permission sets, they should be thoroughly tested to ensure that Skedulo users can access all the objects that are required. Failing to enforce the correct field-level permissions may result in Skedulo not working correctly. For this reason, we recommend applying one of the standard Skedulo permission sets, even if your organization is using custom sets.
Very Important
It is especially important to assign the Skedulo Base permission set to users that do not already have one of the others. Users with only custom permission sets will not receive access to new Skedulo objects to be released in future updates and may run into issues using the application.
Using either Skedulo Resource or Skedulo Scheduler permission sets (based on the role of the user) is preferable to the Skedulo Base permission set. The latter one is only used in the case that you have stringent security controls that cannot be satisfied by the Skedulo Resource permission set.
Skedulo has six standard permission sets; these are listed below along with the types of tasks that they enable.
-
Skedulo Scheduler Permission Set.
Schedulers can access the Skedulo web app to perform the following tasks (note–this is not a comprehensive list):
Create new jobs.
Allocate resources to jobs.
Delete job allocations.
Notify resources of new job allocations or job modifications.
View job travel and routing information.
Create activities.
Create and approve unavailability requests.
Manage resource information.
View/manage job exceptions.
-
Skedulo Resource Permission Set.Resources, such as field-based employees, can access Skedulo via the Skedulo mobile app to complete the following tasks (note–this is not a comprehensive list):
Confirm or decline new job allocations.
View job details.
Start travel, check-in, start and complete jobs.
Retrospectively update job time-stamps.
Create follow-up jobs.
View previous and future jobs at the same location.
Create unavailability requests.
Create activities.
-
Skedulo Base Permission Set.
This gives the user "Read" permission for all Skedulo objects.
Any field that is hidden in the current "Skedulo Resource" permission set will also be hidden in this set. The other permissions are disabled (i.e., create, edit, delete, view all and modify all).
This set defines the minimum permissions required for a Skedulo user. Users that are not assigned either a "Scheduler," "Resource" or "View All" permission set should at least be assigned "Skedulo Base."
-
Skedulo View All Permission Set.
This can be assigned to users who need to view Skedulo data in Salesforce for reporting purposes but do not need to use the Skedulo web or mobile apps.
This read-only permission set will be implemented to give "View All" permission to all Skedulo objects and "Read" permission for all fields within each object. It will thus allow the user to view all Skedulo data in Salesforce, regardless of the owners.
-
Skedulo API User Permission Set.
To be used with the defined API user for the organization. The API user permission set comprises:
A Skedulo "Base" permission set (as a minimum).
"View All" permissions for the "Platform Event" object type (sked__Change_Event__e).
"View All" permissions for the "Resource" object.
"Modify All" permissions for the "Job" and "Resource Requirement" objects.
"Modify All" and "Create" permissions for the "Job Allocation" object.
-
Skedulo Resource Without Assigned Apps Permission Set.
Required for users with "Community User" and "Community User Login" licenses.
-
Skedulo Community Resource Permission Set.
Required for users with licenses other than "Community User" and "Community User Login" licenses such as "Partner Community" licenses.
In addition to assigning these users the "Skedulo Community Resource Permission Set," extra sharing rules will need to be configured.
Note
Managed package permission sets cannot grant any access to a standard object—it is blocked. Permission sets outside the managed package can still grant permission to standard objects and fields. Refer to: https://salesforce.stackexchange.com/questions/108225/managed-package-validation-error
You can view the Skedulo permission sets:
Using Salesforce Classic: Setup > Manage Users > Permission Sets.
Using Salesforce Lightning: Setup > Users > Permission Sets.
The CRM administrator can change or add a user's Skedulo permissions performing the following:
Using Salesforce Lightning: Setup > Users > Permission Sets.
From the permission sets available, click on the one required (in this example "Baseline" will be used).
In the open permission set, click the "Manage Assignments" button. This opens the "Assigned Users" panel.
Now it is possible to add or remove users from the permission set using the "Add Assignments" or "Remove assignments" buttons.
Comments
0 comments
Article is closed for comments.