User management in MyQ X involves three connected decisions that need to be made and implemented in order.
Decision 1. Job Detection Method
When a print job arrives at MyQ, the server needs to match it to a user. The attribute it uses to do this – the job sender name from the print driver, a PJL field, or the job filename – determines what value must exist in each user's MyQ account for jobs to authenticate successfully.
Decision 2. Map Synchronization Attributes
When users are imported from Active Directory, Entra ID, or another source, MyQ maps directory attributes to user properties. The username field – or the alias field – must be populated with the same value that job detection will look for. If job detection expects sAMAccountName but sync only populates UPN, jobs will not match.
Decision 3. Authentication Method
How users log in to terminals, the web interface, and client applications is a separate decision from how their print jobs are identified. However, it interacts with sync: ID card numbers, PINs, and aliases can all be imported from a directory source, and the choice of authentication method determines which of these need to be present and correctly mapped.
The practical consequence is that sync configuration should not be finalized until the job detection method is confirmed, and authentication configuration should be designed together with synchronization.
For step-by-step configuration of sync sources and authentication settings, see the MyQ X Server guide.