Overview 

This guide has generic steps to exclude a specific driver from Geotab access through the Eleos platform. This process will remove the user based on the matching ManPowerProfile ID.  The location to make this change is different depending on whether SQL contracts are implemented for your company. To determine your company’s set up, locate the ELEOS.usp_ValidateUser_Custom_Template stored procedure in the database.  If this procedure exists, that indicates that SQL contracts are implemented, and changes will be made in ELEOS.usp_ValidateUser_Custom_Template.  If ELEOS.usp_ValidateUser_Custom_Template procedure does not exist, within your database, then that indicates that SQL contracts are not implemented, so the changes will need to be made to the ELEOS.usp_ValidateUser instead to exclude a Geotab user from Eleos.  The following sections outline the steps for both scenarios.


Locating and Changing the SQL File

With SQL Contracts implemented, instructions to make updates can be found in the ELEOS.usp_ValidateUser_Custom_Template procedure. To exclude a user from Geotab, first check the temporary table containing this information, #ASR_ValidateUser_Drivers, then manually set the [UseGeotab] value to false for specific users before returning the results. The default for most clients is @True to start if they use Geotab.  Below is a screenshot portion of the documentation for the ELEOS.usp_ValidateUser_Custom_Template procedure where it talks about making modifications to the temporary table:

The modification can be made using the following scripting and input driver usernames where DRIVER1 and DRIVER2 are shown as placeholders below: 

;UPDATE #ASR_ValidateUser_Drivers 
SET      [UseGeotab]        = CASE WHEN [Username] = 'DRIVER1' 
                    OR [Username] = 'DRIVER2' 
                                        THEN '@False’
                                        ELSE '@True'
                                    END

Re-Including Geotab Users

To re-include users that were excluded from Geotab, remove the updates (made using the steps above) or drop the ELEOS.usp_ValidateUser_Custom_Template procedure entirely if no customizations are required anymore. To do this for a single user that needs to be re-included, delete the user from the case statement. 


Without SQL Contracts Implemented

In the ELEOS.usp_ValidateUser code locate the “[UseGeotab]” variable where it is being assigned. The right of the assignment operator should contain a CASE statement that evaluates @False when the users ManPowerProfile ID matches a specified string and evaluates @True otherwise:

To exclude a new user from Geotab, extend the CASE statement using an additional OR operator and assign the ManPowerProfile ID to the specific string matching the driver’s ID. For demonstration purposes we add “ASR_MPP_4” and “ASR_MPP_5” to the list of excluded users:

These specific users will now be unable to access Geotab through the Eleos platform. Note that these changes can be reverted to reinclude users as well.


Re-Including Geotab Users

If circumstances have changed and there are users that need to be included again, re-including them is simple as removing all or some of the previously discussed case statement.


For example, suppose that users with the ManPowerProfile ID ASR_MPP_5, ASR_MPP_4, and ASR_MPP_3 need to now be included when they were previously excluded. Simply remove those three lines from the case statement in the screen shot above. Now only the first two users remain, as shown in the screenshot below.

Note: Be sure to include the end parentheses after the final line.



If every single user needs to be re-included, instead replace the entire case statement with @True, as shown in the screenshot below.