Versions Compared

Old Version 18

changes.mady.by.user Andrius Č.

Saved on

compared with

New Version 19

changes.mady.by.user Andrius Č.

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Import must be enabled in settings in order to import users.

Import file must be csv format, delimiter is semicolon ";" (without quotes).

First row is used for header, and cannot be changed and must use default naming (if custom headers are used, use "Import wizard" to import users with custom file).

Next rows represents individual users, who must have unique First name, Last name, Employee ID and identifications.

If user doesn't have information on some header, that header can be empty (for example middle name is skipped: first name;;Last name;...)

User photos is stored in assets folder as .jpeg format.

Note

Export files from CredoID  4.1.0 versions and older are not compatible with current CredoID V4


Info
titleImport file fields requirements

If these fields configured incorrectly, import will fail or be incomplete:

  • Custom access levels - needs to be created in the CredoID before user import;
  • User Locations - custom location must be created before user import. Default location must be assigned to all the users;
  • Access levels locations - if not defined, will not be added to the users.




Import Wizard

Import wizard allows to import users from csv, txt files, which headers don't match CredoID headers.

Press "Import Wizard" button and select custom import file. After selecting the file, wait until file is loaded.

"Column Name" field represents header values read from the custom import file.

"Map to field" represents header values required for CredoID import.

Required fields are:

  • FirstName;
  • LastName;
  • Location1.Name;
  • EmployeeNumber;*
Info

*EmplyeeNumber may be not required, if at Settings → User import, Primary key is set to "First and Last name".

After mapping fields, if all required fields are mapped, import should be available.

Press "Download CSV" to download generated import file, which matches CredoID requirements (optional).

Press "Import" to import users after mapping.


Import errors

Anchor
Import errors
Import errors

Error messageError meaningHow to fix
Duplicate record 'x' line n (already seen on m line)This error means that import file contains at least 2 identical lines with primary key "First and Last name" or "Employee number" (depending on import settings).Give all the users unique primary keys: "First and Last name" or "Employee number" (depending on import settings). 
At least one location is required for user. Line n. Primary key: y
User doesn't have location assigned in the import file.Assign at least 1 location to the user. (Default: Main location).
Location 'x' not found in system on line n. Primary key: y
User have a location assigned in import file, that doesn't exists at CredoID.Remove location from this user at import file or create location with the same name at CredoID.
Access level 'x' not found in system on line n. Primary key: y
User have a access level assigned in import file, that doesn't exists at CredoID.Remove access level from this user at import file or create access level with the same name at CredoID.
Duplicate card found 'x' on line n. Primary key: y2 users in the import file have exactly same cards.Remove the card from one of the users.
Removed identification ('x') from user 'Firstname', 'Last name' id: y
Import file contained the card which was assigned to different user in CredoID.This is just a warning, which means that existing card was assigned to the new user after import.
Primary key 'x' is duplicated in systemMore than 1 user exists with primary key "First and Last name" or "Employee number" (depending on import settings) in CredoID.

Find the users with 'x' value in CredoID and give them unique value.

If at import settings, employee number is used and users were created before enabling this settings, all blank employee numbers are treated as duplicates. Assign Employee numbers to the users which doesn't have it at CredoID.

If at import settings, First name and Last name is used, users with exact same values exists in CredoID, change import settings primary key to the "Emplyeenumber" if user first name and last name cannot be updated.

















Active Directory

Users can be imported from Active Directory using CredoID Active Directory import module.

How to import users from Active Directory

User Binding
  • Navigate to "Users " tab.
  • Click "Import" button:
    • Active directory settings window will appear:
  • Save as scheduled import - save current import as scheduled import, which can be executed periodically. More information can be found at "Automation → Imports".
  • Primary key - select primary key (First and Last name or Employee number). Primary keys must have unique values.

    • Mode:

    ModeDescriptionOverwriteAdd new users and Overwrite existing user data at CredoID.  If user already exists, all user data is updated according to import source.AppendAdd new users and add data to existing user if existing user data fields was empty before import.SynchronizeSame as "Append". User from CredoID are deleted if  doesn't exists at import source.

  • LDAP Path - full path of Active directory (example: ldap://1.2.3.4:389/OU=users,DC=midpoint)

  • LDAP group path -  full path of Active directory group. Users existing in this group will be assigned with access level, after binding groups to access level (example: ldap://1.2.3.4:389/OU=groups,DC=midpoint).
  • Username - user name for LDAP login.
  • Password - password for LDAP login.
  • After entering all required data, click "BINDINGS" button.
    • If connection to LDAP server is successful, "Import bindings" window will appear:
  • CredoID column - represents user field in CredoID.

    • Attribute - select binding field form Active Directory available user fields.*

    Info
    titleRequirements for Active Directory fields
    • All fields must be single valued except locations and identifications.
    • Activation/Expiration fields require to follow ISO 8601 date and time format.
    • Identifications fields must follow one of formats:
      1. as card/pin string: cardbits_facilitycode_cardnumber_pin (example: 26_10_12345_1234)

      2. as JSON string:
        {

            "CardNumber": "12345",

            "FacilityCode": "10",

            "VisibleNumber": "12345",

            "CardFormatBits": 26,

            "PinCode": "1234",

            "LicensePlate": "MDP23"

        }

  • Click "Group binding".
  • Select access level on the right column, which will be applied to available Active directory group from left column.

    • Image Removed

    Image Removed

    Image Removed