Overview

 

Skedulo platform and Skedulo for Salesforce orgs can use custom roles and set functional permissions to control user access to application features and data.

Custom roles allow administrators to create new roles outside of the standard Administrator, Scheduler, and Resource roles and assign access-level permissions to each of them.

Functional permissions and custom roles give administrators fine-grained control over the features and data that users can access. 

Permission settings apply to the following application functions:

• Application features, such as the ability to dispatch a job.
• Navigation options available to the user in the web app. 
• Platform features, such as creating messaging channels.
• Administrative controls, including adding users and modifying their permissions.
• Creating and modifying shared list views.
• Access to Skedulo APIs.

Multiple role assignments

Admin users, and other users with appropriate role permissions, can assign custom roles instead of, or in addition to, the standard roles.

Users with multiple roles are granted all of the permissions from their assigned roles.

For example, you may want certain users with a Resource role to also be able to log in to the web app to view their schedule. To do this, you can modify the Resource role permissions directly to provide all users with the Resource role access to the web app. 

Alternatively, you can create a custom role with web app permissions and assign it to the users with a Resource role so that they have all of the usual Resource role permissions as well as the custom role permissions that provide them with access to the web app.

You can also remove permissions for standard user roles by modifying the role directly. 

 

Base permission requirements

A user can access the Skedulo web app with only a custom role; they do not need to have one of the standard roles. Users must have the Resource role to be assigned work and use the Skedulo mobile app to complete work. 

However, their role/s must have the basic set of permissions that are required to use the apps. These permissions are identifiable in the permissions list with a ⚠️ icon in the description. 

If a user does not have the required set of base permissions, they will receive an error when loading the app.

Standard roles have a pre-defined set of permissions by default, but these standard roles can also be modified.

 

Role management

As a user with the required permissions (or the Administrator role), you can configure roles and permissions in the Skedulo web app.

To view the roles available on your tenant, navigate to Settings > User roles.

From this page, you can:

• Modify permissions for the existing standard Scheduler and Resource roles.
• Reset a standard role to its default values.
• Create a custom role.
  • Roles can be copied from an existing role (recommended) or created from scratch.
• Modify permissions for the new custom role.

To view the roles assigned to users on your tenant (Skedulo Platform only), navigate to Settings > Users.

From this page you can:

• View roles assigned to users.
• Select a user and assign a custom role.

For information on how to modify existing user roles or create custom roles, see Creating custom roles for functional permissions.

Controlling access to functions in the web app

Many permissions affect functions or menu items in the web app.

Some examples include:

• Scheduling → Dispatch resources - Controls the Dispatch button or action in the Job Details, Swimlane, or Grid views and elsewhere.
• Scheduling → Create and send job offers - The ability to create and send job offers.
• Custom Objects and Fields → Modify schema - Controls access to the Settings page for adding custom objects and fields.
• Resource tracking → View resource tracking - Whether the Actual time tab on the Job Details page and the suggested and actual routes on the maps are displayed.

 

Controlling access to the API

Most permissions affect the user’s access to the Skedulo API.

Even if an action is allowed in the Skedulo web app, it may be denied by the API based on the user’s permissions.