Configure Unique Property Generation

How to configure Usercube to generate unique identifiers, mails and logins for any user who does not have them already.

Overview

All users need to:

• be uniquely identifiable through an identifier, for example in order to link all accounts to their owners;
• have a reserved unique email address, even if they do not need a mailbox;
• have a unique login that can be used as a seed for all users' accounts.

For each unique property, Usercube provides a set of generation rules. You are free to choose the most adequate method regarding your actual approach.

An identifier/email/login suffix can be specified later according to users' contract types, when loading identities through an Excel template.

For example, contractors can get -ext added automatically to their email addresses.
The unicity checks performed for identifiers/emails/logins do not consider prefixes nor suffixes.

For example, john.doe@acme.com and john.doe-ext@acme.com cannot exist simultaneously.

Participants and Artifacts

Integrators may need the help of the HR department to understand the actual approach of the organization to compute these unique properties.

Input	Output
Usercube's server (required)	Generation rules for unique properties

Configure Unique Property Generation

Configure the generation of unique properties by proceeding as follows:

1. On the home page, click on Settings in the Configuration section.

   

2. On the Workforce > Identifiers, Mails & Logins page, you can follow Usercube's instructions to configure the generation of a unique identifier for new workers (if needed), based on one of the available options.

   

   • Based on Full Name: replaces all diacritics by the non-accentuated variants; removes all special characters; can add a separator between the first name and the last name if needed (such as . most often); in case of homonyms, appends a sequence number to the full name.

   • Based on Last Name: uses the first letter of the first name; in case of homonyms, uses more letters of the first name up to the whole first name; in case of homonyms still, appends a sequence number to the full name.

   • Random Number: uses a random number with a default prefix which is used when no specific prefix is specified on the user's contract type.

     NETWRIX recommends using random numbers, as they have the advantage of not containing any personal information nor giving any hint about the users' seniority.

   • Sequence: uses a sequence with a default prefix which is used when no specific prefix is configured on the user's contract type.

3. Follow Usercube's instructions to configure the generation of a unique email address for all users (who do not have one), based on one of the available options.

   

   • Based on Full Name: replaces all diacritics by the non-accentuated variants; removes all special characters; can add a separator between the first name and the last name if needed (such as . most often); in case of homonyms, appends a sequence number to the full name.

   • Based on Last Name: uses the first letter of the first name; in case of homonyms, uses more letters of the first name up to the whole first name; in case of homonyms still, appends a sequence number to the full name.

   • Based on Unique Identifier: uses a combination of the unique identifier (defined on the same page) and the email domain.

     No matter the strategy:

     • the default email domain is used when no specific domain is specified on the user's subsidiary;
     • emails are generated in a way that lets users keep their email address, even if they move from contractors to employees, or change to another subsidiary.

4. Follow Usercube's instructions to configure the generation of a unique login for new workers (who do not have one), based on one of the available options.

   

   • Based on Email: uses the local part of the email, i.e. before @.
   • Based on Full Email: uses the full email.
   • Based on Unique Identifier: uses the unique identifier (defined on the same page) prepended with the default prefix when no specific prefix is specified on the user's contract type.

5. Click on the Save icon at the top.

   

6. Click on the Reload button to apply the recent changes to the application.

   

Verify Property Generation

In order to verify the process, add a fictitious employee through the workflows from the UI.

Verify in the directory that the employee's sheet displays the expected values for the configured unique properties.