Queue Types

MyQ X uses four queue types. Each has distinct behavior that determines how and when jobs are released, and which features are available to users. Choose queue types as part of your print environment design – the right combination depends on your security requirements, device fleet, user workflows, and accounting model.

Direct Queue

A direct queue is assigned to a single device. Jobs sent to a direct queue are forwarded to that device immediately and printed without user intervention.

Use a direct queue when:

• Immediate printing is acceptable and secure hold print is not required.

• A device is dedicated to a specific workgroup, department, or function.

• You need per-device accounting without requiring users to authenticate at the device.

A direct queue requires no embedded terminal for basic operation. If an embedded terminal is present, users can still log in and interact with the device, but jobs are not held waiting for release.

Pull Print Queue

A pull print queue holds jobs on the server until the user authenticates at a device and releases them. The queue can have multiple devices assigned to it, and users can release their jobs at any of those devices.

Pull print is the foundation of secure printing in MyQ X. Jobs are not printed until the user authenticates at a device and releases them, which reduces unattended output and helps prevent confidential documents from being printed before the user is present.

Use a pull print queue when:

• Secure hold print is required.

• Users need the flexibility to release jobs at any available device.

• You want to reduce waste from jobs that are sent but never collected.

• An embedded terminal or Mobile Client is available for authentication at the device.

Pull print typically requires an embedded terminal or hardware terminal for release at the device. In some scenarios, devices without an embedded terminal can participate by using a printed QR code with the MyQ X Mobile Client.

Tandem Queue

A tandem queue distributes jobs across multiple assigned devices. Incoming jobs are balanced among the available devices rather than queued for a single device.

Use a tandem queue when:

• A group of users generates enough print volume to create bottlenecks at a single device.

• You want to reduce wait times without requiring users to choose a specific device.

• Load distribution across a device group is more important than user-directed device selection.

Tandem queues are suited to high-volume, time-sensitive printing where throughput matters more than document confidentiality. They are not a substitute for pull print where documents must be held until the user authenticates at the device.

Delegated Queue

A delegated queue extends pull print by allowing designated users – delegates – to release jobs on behalf of another user or group. Jobs sent to a delegated queue can be released by the configured delegates, and are accounted to the delegating user.

Use a delegated queue when:

• Users need to delegate print release to an assistant or a shared role.

• A group of users shares responsibility for releasing documents from a common workflow.

• You need delegated release while keeping jobs accounted to the originating user.

Delegated printing requires defining delegate relationships before go-live. Delegates are configured per user or per group, either by the administrator or by users themselves if self-management is enabled.

Queue Type Comparison

*Or Mobile Client with QR code.

Planning Notes

Most deployments use more than one queue type. A common baseline is one pull print queue covering the majority of users and devices, one or more direct queues for dedicated or shared-access printers where immediate output is appropriate, and delegated queues for specific roles or workflows that require them.

Queue access can be restricted by user or group. When MyQ Desktop Client printer provisioning is configured, queues can be deployed to user workstations based on user or group assignment, so users receive the queues intended for them.

Queue design depends on group configuration and authentication decisions made earlier in the planning process. Finalize your queue structure after group configuration and authentication have been settled, not before.