Quick start for admins
The following is an outline of the basic steps to configure your Dispatcher Paragon Cloud. Your setup may differ according to what kind of queues, authentication, terminals, etc, you are going to use.
For more advanced concepts and settings, refer to the Admin guide, Reference documents, and Legacy documentation.
Prerequisites
Your tenant in Dispatcher Paragon Cloud is created, and you have received your username and password to log in to the Dispatcher Paragon Cloud Web UI.
Configuring authentication
Dispatcher Paragon Cloud supports the following types of authentication:
- Local user authentication – you can create user accounts within Dispatcher Paragon Cloud. Users then log in to Dispatcher Paragon Cloud with these accounts.
- Authentication to external directory – users log in with their existing user accounts from identity providers such as Microsoft Entra, Google, etc. This can be done via:
- OIDC
- Service account (Service access)
- Client-side authentication
For details, see Authentication providers.
Example: Setting up Microsoft Entra authentication using the built-in OIDC
- In Dispatcher Paragon Cloud Web UI, go to Authentication.
- Click Add.
- Fill in:
- Name – Enter an internal name used for identifying the particular authentication provider configuration.
- Type – Select Microsoft Entra ID.
- Domains – Enter your organization's domain or domains. It should match “@domain” part of the users who will use it to authenticate to Dispatcher Paragon Cloud. For example, to allow user john.doe@acme.com to log in via this Authentication provider, enter the acme.com domain here.
- Priority – A number that determines the order in which authentication providers will be called until one succeeds.
- Active – If enabled, this authentication provider will be used for authentication.
- In the OIDC Authentication section, enable the built-in OIDC by selecting Built-in from the dropdown list.
- Click Save.
- By default, every user logged in via this provider will have the Authenticated Users group assigned in Access control section of Dispatcher Paragon Cloud. For more details, see Access Control.
For more information on Entra ID authentication, see Microsoft Entra authentication.
Adding a print queue
Dispatcher Paragon Cloud offers two types of print queues – Direct queues and Pull queues. A Direct queue sends the print job directly to the output printer. A Pull queue sends the job to the Storage Service in Dispatcher Paragon Cloud. When the user wishes to print, goes to an MFD with a Dispatcher Paragon Cloud terminal installed, and logs in, the MFD pulls the print job(s) from Dispatcher Paragon Cloud.
If you wish to use a direct print queue, the simplest way to add it is when registering your MFD. See the next section of this manual – Adding an MFD.
If you wish to use a Pull queue, perform the following steps:
- In Dispatcher Paragon Cloud Web UI, go to Print queues.
- Click Add.
- In Name, enter the name of your queue.
- In Queue type, select Pull print queue.
- Click Save.
For more information, see Print queues.
Adding an MFD
If you wish to use Direct print queues, the only step you need to do is to register your MFDs. See Printers.
If you wish to use Pull print queues, your MFDs must have Dispatcher Paragon Cloud terminals installed. The installation method differs according to the MFD brand and according to the type of the terminal:
- Pure cloud terminals (for MFDs that can connect to the cloud directly)
- Terminals that require a Dispatcher Paragon Cloud secondary gateway in your network
See Embedded Terminals.
In general, the process always consists of:
- Doing the MFD-specific setup in the MFD UI. Either directly at the MFD, or in the MFD's web interface. This is described in the guide for each brand in the Embedded Terminals section.
- Creating the Embedded configuration for the particular brand of MFD. See Embedded Terminals' configuration.
- Registering the MFD in Dispatcher Paragon Cloud Web UI. See Printers.
- Installing the terminal on the MFD. Depending on the type of the terminal and the MFD brand, you can do this by one (or more) of the following options:
- Deploying the Embedded configuration to the MFD from Dispatcher Paragon Cloud Web UI. See Embedded Terminals' configuration, section Deploying the configuration.
- Installing the terminal via a command-line tool from your PC. See Terminal Deployment Tool.
- Installing the terminal from the vendor's marketplace or app store. E.g. Konica Minolta or Ricoh.
Installing Dispatcher Paragon Cloud Client
Dispatcher Paragon Cloud Client is a desktop application that can be installed on end-user workstations to create print queues and install the Dispatcher Paragon Cloud universal driver automatically. For its features, see Dispatcher Paragon Cloud Client.
The Client can operate in two modes: Local storage mode and Gateway mode. For details, see Dispatcher Paragon Cloud Client overview.
Both modes can be used in the Pure Cloud printing scenario, but we recommend using the Local mode. In the Pure Cloud printing scenario, the Gateway mode has the following limitations:
- Direct printing is not possible.
- Releasing the print job from the Mobile application is not possible.
The following steps describe Quick installation (preconfigured installation without advanced options). For more details about the difference between Quick installation and Advanced installation, see Installing Dispatcher Paragon Cloud Client on Windows and Installing Dispatcher Paragon Cloud Client on macOS.
- To download the latest version, log in to Dispatcher Paragon Cloud Web UI and go to My documents. Click the button corresponding to your operating system and save the Client installation file.
Run the saved Client installer file.
- Follow the installation wizard. On the Installation Type screen, select Quick installation (you will only see this screen in the Windows installer. The MacOS installer does the Quick installation by default).
When the installation finishes, you will see a login screen in your web browser.
Note that if the option to Automatically trust new clients/servers is disabled in the Security menu of Dispatcher Paragon Cloud Web UI, you will need to authorize each end user's Dispatcher Paragon Cloud Client in Infrastructure > Endpoints.
- After you log in, the print queues you created in Dispatcher Paragon Cloud Web UI will be synchronized and visible in your Printers and scanners.
For silent installation and the available command line parameters, see Installing Dispatcher Paragon Cloud Client on Windows and Installing Dispatcher Paragon Cloud Client on macOS.
For deployment via Microsoft Intune, see Deploy Dispatcher Paragon Cloud Client using Microsoft Intune.
Mobile printing
- Log in to Dispatcher Paragon Cloud Web UI.
- Go to Mobility print.
- In Mobile print service, select mobileprint service. Leave the other settings at their default options.
- Click Save.
- Download the Mobile app using the links in My documents section. See My documents.
- Submit your print job using the Mobile app.
For more information on how to use the Mobile app see Using the legacy Mobile app.
Releasing a print job at the MFD
You can authenticate at the MFD via card, PIN (short ID), username/password, or combination of these methods.
For generating a PIN, see My profile.
For card self-registration at the MFD, see Card registration at the MFD.
After logging in at the MFD, you will see the My Quick Actions screen. Tap Print all or My print jobs.
Configuring a password policy
If you plan to use local user authentication, we recommend you to configure a password policy. See Password policy.
Gateways (edge devices)
With Dispatcher Paragon Cloud, you can use a gateway (secondary server) on your site to route traffic securely between the cloud and the MFDs. Using a local gateway, the print job data do not have to leave the company network, increasing security, responsiveness, and reducing Internet bandwidth. The gateway can be compared to simple devices routing data, such as network routers.
Our recommended option is the OMNI Bridge. For other options, see Gateway Guide.
For more information about YSoft OMNI Bridge, see Setting up OMNI Bridge.