Skip to main content
All CollectionsGetting Started
User Segments - ‘Locally Managed’ and ‘Local Authentication’
User Segments - ‘Locally Managed’ and ‘Local Authentication’

‘Locally Managed’ and ‘Local Authentication’ user segment rules

Updated over 6 months ago

The ‘Locally Managed’ user segment removes user from potential of being marked 'inactive'.

Your organization may be using an HRIS, HRMS, or HCM service to provide user information to WorkDove. While this method for managing personnel information helps to streamline data management, there are certain cases where you might want selected users to use WorkDove to maintain records rather than your organization’s HR system of record (E.g. a temporary employee might not use the HR system of record).

If you choose to add a user to the ‘Locally Managed’ user segment, you will find that:

  • Locally managed users will not be deactivated from WorkDove if they do not exist in your HR system of record;

  • If a locally managed user does exist in your HR system of record, their records will still be transferred into WorkDove.

The ‘Local Authentication’ user segment removes user from having SSO credentials.

Your organization may be using a single sign-on portal to help employees navigate to your organization’s commonly used websites and apps without having to sign in multiple times across different sites. This alleviates the employee’s need to remember multiple passwords, but it might not be useful for every employee to have (e.g. if an employee has a very limited scope of websites or apps that they need to use, compared to other employees).

We use the ‘Local Authentication’ user segment when it makes sense to have a user sign in with their own unique password for WorkDove, rather than through an SSO that other employees within your organization use. If an employee belongs to the ‘Local Authentication’ user segment:

  • They will use their work email address as their WorkDove user name,

  • Admins can send the employee a Welcome Email so that the employee can create a unique password,

  • The employee is able to select the ‘Forgot your password?’ button on the WorkDove app landing page if they have trouble signing in, and

  • The employee will not be able to sign in using their SSO (should they eventually be credentialed) until they have the ‘Local Authentication’ user segment removed in WorkDove.

If you have additional questions about user segments, please contact us at [email protected].

Did this answer your question?