User synchronization is a method of importing and periodically synchronizing user-related data in the MyQ database with data in external sources, such as Microsoft Entra ID, LDAP servers or CSV files. Importing new users is an optional part of the synchronization process. Within the synchronization setup, you can activate or deactivate the new users import; if you deactivate it, MyQ only updates accounts of users that already are in its database.
This section provides detailed information about synchronization. It fully describes the methods of import and synchronization available in MyQ and presents two options of running the synchronizations:
User passwords are not synchronized/stored in the MyQ Database in case of LDAP/MS Entra ID synchronizations.
Which Properties Can Be Synchronized
When MyQ synchronizes users from a directory service or CSV file, it maps source attributes to MyQ user properties. Not all user properties can be populated by synchronization, and not all properties behave the same way across sync sources. This page summarizes which properties can be synchronized, their constraints, and the default attribute mappings for each source type.
|
MyQ Property |
Syncable |
Constraints |
|---|---|---|
|
User name |
Yes |
Fixed per source type – always |
|
Full name |
Yes |
No constraints. |
|
Aliases |
Yes |
Multiple values accepted, comma-separated. Used to match jobs sent with identifiers other than the username. |
|
Personal number |
Yes |
Must be unique per user. Used for pairing users across sources. |
|
|
Yes |
No constraints. |
|
Alternate emails |
Yes |
Multiple values accepted, comma-separated. |
|
Phone |
No |
Must be set manually. |
|
Department |
Yes |
No constraints. |
|
Cards |
Yes |
Sync mode configurable: Do not synchronize / Full synchronization / Synchronize if not empty / Add new. Multiple values accepted, comma-separated. |
|
PIN |
Yes |
Sync mode configurable: same options as Cards. In CSV, PIN values must be in hashed MD5 format. Multiple values accepted, comma-separated. |
|
Default language |
Yes |
Value must be a supported language abbreviation, for example |
|
User's storage |
Yes |
No constraints. |
|
Notes |
Yes |
No constraints. |
|
Custom (1-3) |
Yes |
Available for Entra ID (Graph API) and CSV sources. Map any attribute not covered by standard properties. |
|
Use authentication server |
Yes |
Set at the sync source level – applies to all users imported by that source. Not mapped per user. |
|
Synchronization source |
Automatic |
Set by MyQ based on the sync source name. Not configurable per user via sync. |
|
Advanced (on-premises identity) |
Automatic |
Populated automatically for hybrid Entra ID users from |
Default Attribute Mappings by Source
Where a default mapping exists, MyQ applies it automatically. Properties with no default must be configured explicitly in the sync source settings.
Active Directory (LDAP)
|
MyQ Property |
Default AD Attribute |
Notes |
|---|---|---|
|
User name |
|
Fixed. |
|
Full name |
|
|
|
|
|
|
|
All other properties |
(none) |
Must be configured explicitly. |
Commonly configured explicitly:
|
MyQ Property |
Recommended AD Attribute |
Notes |
|---|---|---|
|
Alias |
|
Map here if job detection returns UPN. |
|
Alias |
|
Map here if job detection returns email-format identifiers. |
|
Personal number |
|
Useful for pairing across sources. |
|
User's storage |
|
Enables Easy Print from / Easy Scan to user's home folder. |
|
Card, PIN |
Custom or |
Review confidential attribute protection before enabling. |
Microsoft Entra ID (Graph API)
|
MyQ Property |
Default Attribute |
Notes |
|---|---|---|
|
User name |
|
Fixed. |
|
Full name |
|
|
|
|
|
|
|
Language |
|
|
|
Department |
|
|
|
All other properties |
(none) |
Must be configured explicitly. |
Available attributes for explicit mapping include employeeId, mailNickname, upnPrefix, onPremisesSamAccountName, onPremisesDomainName, and extensionAttribute1 through extensionAttribute15. Any Entra ID user resource attribute can also be typed manually if not listed in the dropdown.
OpenLDAP
|
MyQ Property |
Default Attribute |
Notes |
|---|---|---|
|
User name |
|
Fixed. |
|
Full name |
|
|
|
|
|
|
|
All other properties |
(none) |
Must be configured explicitly. Schema varies by installation – verify attribute names in your directory. |
Novell eDirectory
No default mappings. All properties must be configured explicitly. Use the LDAP browser in the sync source General tab to identify attribute names in your directory.
Google Workspace (Secure LDAP)
|
MyQ Property |
Typical Attribute |
Notes |
|---|---|---|
|
User name |
|
|
|
Full name |
|
|
|
|
|
|
|
All other properties |
(none) |
Verify attribute names against your directory using the LDAP browser. |
CSV
All properties are mapped by column name (or column position if no header row).
Sync Mode Options for Cards and PIN
The following sync modes apply to Cards and PIN properties across all source types that support them.
|
Mode |
Behavior |
|---|---|
|
Do not synchronize |
Existing values in MyQ are not changed. |
|
Full synchronization |
Existing values are replaced with values from the source, including replacement with empty if the source value is empty. |
|
Synchronize if not empty |
Existing values are replaced only if the source value is not empty. Default for CSV. |
|
Add new |
New values from the source are added without replacing existing ones. |