With the Equus Platform supporting management for the Remote Work population, there are two ways to initiate a Remote Work Request
Self-Service Request
A Remote Work Request Form has been created that will allow users to submit Remote Work Requests for themselves. This form can be accessed by Internal, External Client, External Payroll, and Employee users. This form and configuration is located at the company level. This is available to both SSO and non SSO users.
SSO Users
SSO users will follow the same steps in accessing the Equus Platform to access the form and a user will be created for them once they access the form.
Auto-provisioning needs to be set up for Remote Work requests. Separate from standard auto-provisioning, user records created through this auto-provisioning will always have a User Type = 'External Employee' and 'Employee Experience'
Users who have a User record created through Remote Work auto-provisioning may also have additional User records generated through standard auto-provisioning. Similarly, SSO users with an existing user type in the system (e.g., internal users) will have a separate User record created when they log in to the Remote Work form.
Similar to SCIM API with multiple logins, these users will see option to select which user type to login. When accessing the Remote Work Request form, they should select the Employee user type to avoid potential issues with HRIS integration.
Non SSO Users
Non-SSO users will need to log in with their credentials to access the form. This should follow your process on creating access credential as the form can be accessed by Internal, External Client, External Payroll, and Employee users.
Employee Record
The platform will verify if the employee account of the user and will follows the Equus Platform's validation process of checking to see if there is an employee linked to that user.:
If there is a user, it will use that employee account.
If no employee account is linked, a search is done to see if there is an un-linked employee account with a matching first name, last name, e-mail address, and company. If there is, the account is linked to the user. The company will based to the company associated to the company associated in the URL
If we are unable to link an existing employee account, a new employee account is created for that company and linked to that user account.
Users that submit request for multiple companies can have an employee account created for each of those companies. This means 1 user can have multiple employee accounts linked to it, but no more than 1 per company.
Initiate on someone’s behalf
Mobility-initiated requests using the Mobility Manager Widget in a Landing Experience Dashboard, where users can either create new case records via a dynamic data-entry form, or view and edit existing ones.