Web Print requires an additional license. Contact your Vasion representative for details.

Configuration steps in the Admin Console are not visible without licensing.

Review the following key points:

• Web Print uses the same logo as the Self-service Portal.
• You can configure the Web Print Portal to require authentication for internal users.
  • When using authentication Web Print works with Quota Management to track printing usage and enforce limits.
• If you turn on guest printing, the user prints using their email and a release code.
• Web Print supports, Pull Print, Direct Secure Release, and Delegated Release. For more details refer to Secure Release Print.
• The printers you designate for Web Print do not work for normal Secure Release Print with prompts. Prompts appears when using Web Print, but devices do not show the prompts when printing outside of this feature.

For more details refer to Web Print.

Review the following requirements:

• Web Print requires additional licensing. Contact your Vasion representative for more information.
• You must turn on and configure ONCP for the selected printers. For more details refer to Off-Network Cloud Print (ONCP).
• For authenticated users or guests to release held jobs at the printer, you must install the Secure Release Print feature on the printer.
• Add print-api.app.printercloud.com, adjusted for your region
  • U.S.: printercloud.com.
  • EMEA: printercloud5.com.
  • Azure: printercloud6.com.
  • APAC: printercloud10.com.
  • Canada: printercloud15.com.
  • Singapore: printercloud20.com.
  , to your firewall rules. For more details refer to Requirements & Supported Environments.
• Some Fujifilm devices require a PostScript (PS) module to use the Web Print feature.

Only printers configured for ONCP appear as selectable options in the Web Print settings. Printers without ONCP do not appear in the printer selection modal.

The type of users (authenticated / guests) and how they release print jobs determines if your environment requires installing the CPA Secure Release Print feature.

Authenticated Users

Review the following about authenticated users:

• Users authenticate to the portal using their identity provider credentials.
• Web Print works with Quota Management to track printing usage and enforce limits.
• Releasing jobs using the PrinterLogic mobile app does not require the Secure Release Print feature.
• If the user releases the job at the printer, you must install the Secure Release Print feature on the printer.

Guest Printing

Review the following about guest printing:

• You must turn on Allow Guests in the Web Print settings.
• The user enters their email address to authenticate to the Web Print Portal.
• Because guests have no other release method available, you must install the Secure Release Print feature on the printer with Web Print code authentication turned on.

You can install Secure Release Print and Web Print code authentication at the same time from the printer's Apps tab. If you use the CPA Manager, install Secure Release Print first, then add Web Print code authentication using the Modify option.

The release prompt that appears when a user prints depends on the Secure Release Print setting configured for each printer. Review the options below and confirm your printers are set correctly:

• No: Jobs print immediately and cannot be held.
• Yes (Always): Jobs hold automatically and require the user to release them.
• Yes (Prompt): The user selects either Hold or Print Now.

To change the global default, go to Tools Settings Printing, scroll to the Pull Printing section, and select your preference in the Default per-printer Secure Release settings menu.

To override the setting at the printer level, open the printer object, select the Printing tab, and change the selection in the Allow secure release jobs to be sent to this printer menu.

For guest printing, the Hold option requires Secure Release Print installed on the printer. If you do not install Secure Release Print, configure printers to use Print Now for guest jobs.

PrinterLogic authenticates users at the printer control panel through IdPs like Entra ID (Azure AD), Okta, Active Directory, and more.

Review the Supported IdPs and configure your identity provider before moving onto the next section.

• Active Directory (AD)-based IdPs (LDAP with Identity Sync and Active Directory Query eXecutor (ADQX)) support username / password, badge, and PIN authentication at the CPA.
• Cloud-based IdPs (Entra ID (Azure AD), Okta, Google Identity, etc.) only support badge and PIN authentication at the CPA.

For topics and steps setting up attributes in your IdP, refer to Badge & PIN Management and the section's subtopics.

Before testing authentication, confirm that users have been provisioned into PrinterLogic.

1. In the Admin Console, go to Tools Identity Management or Tools Identities, depending on enabled features.
2. Confirm that your provisioned users appear in the list.
3. Select a user and verify that the badge or pin shows up.

Users in the Identity Management table can sign in to the Self-service Portal and the Agent.

Follow these steps to turn on the Web Print Portal:

1. In the Web Print section, select the Enable Web Print option.

2. Select Save.

   

After you turn on Web Print, use the link in the Web Print section to visit your Web Print Portal. If you are not using the Allow Guests option or Secure Release Print, Web Print is ready to use.

The logo that appears in the Web Print Portal is the same logo you upload in Tools Settings Portal. Update your logo there if needed.

This setting makes the Queue tab appear on printer objects. You use the Queue tab to view the printer queues on end user devices, and this setting makes jobs visible to the local spooler for release.

Review the options in the Default per-printer Secure Release settings section. Most are optional and support additional enhancements or features, but the prompt settings directly impact Direct Secure Release. Know which ones you plan to enable before continuing to the next step.

The following are additional options:

Allow End-Users to Override

This option lets the user set their release printers and turn on prompts to hold or print, which are accessible from the system tray icon and the secure print settings in the operating system (OS) menu. For more details refer to the Secure Print Settings Guide.

Back End Release: Automatically release held jobs to printers with Yes (Prompt) set

With this option selected, when the user sends a print job to a printer with Yes (Prompt) selected, the job automatically releases to the printer rather than being held. You typically use this option in environments in which the printer is in a secure location, such as a private office.

This option appears only for customers using PrinterLogic Output.

Enable Offline Secure Release Printing

This option requires a Service Agent. When a user holds a print job, the Service Agent creates a copy. If the user's device is offline or the user is signed out, they can still release their held job to the printer, which prints the copy from the Service Agent. For more details refer to Offline Secure Release Print (OSRP).

Release Prompt Settings

The release prompt that appears when a user prints differs depending on how you configure the Secure Release Print settings for the printer. You select from the following options:

• No: Jobs print immediately and cannot be held.
• Yes (Always): Jobs automatically hold and require the user to release them.
• Yes (Prompt): The user is prompted to select either Hold or Print Now.

Configure prompt settings globally or per-printer.

Follow the steps in the chosen section below to turn on Direct Secure Release globally or on a per-printer basis.

This section covers configuring a Service Agent which installs Vasion apps and features on a printer, like Direct Secure Release, Copy / Scan Tracking, and more.

If you already have a configured Service Agent, still review the requirements and steps below before continuing to the next sections.

Device Requirements

• Device:
  • Windows 10 or 11 and Server 2016, 2019, 2022, or 2025.
    • Visual C++ Redistributable for Visual Studio 2015-2022 package or later.
      • You must install both the x86 and x64 redistributable packages. You can download these packages from the Windows Download Center.
      • The Service Agent cannot be a Windows device using an ARM processor.
  • macOS with an Intel processor.
  • Ubuntu Long Term Support (LTS) 22.04, 24.04, or 26.04.
• Dual-core processor.
• 20 GB of available hard drive space.
• 8 GB of RAM.
• PrinterLogic Agent installed and authorized.
• The device, such as server, virtual machine, or workstation, must have network access to target printers.
• The device must remain powered on because shutting it down stops all services.

Additional CPA Requirements

The number of printers with the CPA An app installed on a compatible multifunction device (MFD) that aids in the release of held print jobs, supports authentication for secure printing, and provides simple scanning functionality. installed that a single Service Agent or Independent Service Manager (ISM) can support depends on the device's resources and operating system (OS). Windows and Linux devices that follow the CPA requirements below support around 1,000 printers. If you have a large environment with 1,000 or more printers using the CPA, consider adding an additional Service Agent or ISM.

Requirements for the CPA Printer Apps service include the following:

• The device running the Printer Apps service must be on the same network as the printers it manages.
• For every 100 printers, add an additional 2 GB of RAM to the minimum listed above.
• If your environment uses Single Sign-On (SSO), monitor RAM usage and increase the RAM as needed to handle increased memory usage during check-ins.
• On macOS and Linux, the Service Agent running the PrinterLogicServicePrinterApp.exe service must have OpenSSL 3.5 or later installed. On Windows, the Service Agent installation already includes this requirement, so no separate installation is needed. For more details refer to OpenSSL Documentation.

For more details refer to Service Agents.

You must install and authorize the Agent on the device acting as your Service Agent before you define it in the Admin Console.

If the Agent is already installed and authorized on this machine, you can mark this step complete and move on.

Install the Agent & Web Extension.

To create the Service Agent object in your tree structure:

Follow these steps to create a new Service Agent:

1. Sign in to the Admin Console.
2. Select the folder in which you want to place the Service Agent.

3. Select the New button at the top of the tree structure.

   

   1. Alternatively, you can right-click the folder and select New Service Agent.

      

4. In the Name field, give the Service Agent object an identifiable name.
5. In the IP Address or Hostname field, enter the IP address or Fully Qualified Domain Name (FQDN) The complete domain name for a specific device or host on a network, consisting of the hostname, the domain name, and the top-level domain. of the device that hosts the Service Agent.

6. Select Add Service Client.

   

The name can be anything descriptive. If using a hostname, use the FQDN, for example printserver01.example.com.

With the Service Agent object created, turn on the Printer Apps service.

Follow these steps:

1. Go to the Service Agent's Printer Apps tab.

2. Select Enable Printer Apps.

   

3. Select Save.
4. Access the device designated as the Service Agent.
5. Use the system tray icon or Start menu to refresh configurations.
6. Open the Task Manager, and select the Details tab.
7. In the Search field, enter printer to locate the Agent services.
8. Confirm that the following services are running:
   1. Agent services, which include VasionClient.exe, PrinterInstallerClient.exe, PrinterInstallerClientInterface.exe, and PrinterInstallerClientLauncher.exe.
   2. PrinterLogicServiceManager.exe.
   3. PrinterLogicServicePrinterApp.exe.

Other active services on the Service Agent also appear.

The folder structure creation for the new service takes a minute. Once complete, the service begins running and you can view it in Task Manager or similar management apps.

If the service does not start after a couple minutes, and doesn't create the folder structure, select Reauthorize on the General tab of the Service Agent object, then refresh the Agent on the Service Agent device.

You can install Web Print code authentication in one of two ways:

• Apps tab (individual): Installs Secure Release Print and Web Print code authentication on a single printer at the same time. Use this method for targeted deployments.
  • For prerequisites and supported printers, refer to CPA 2.0.
• CPA Manager (bulk): Installs across multiple printers from the same manufacturer simultaneously. You must install Secure Release Print first, and then add Web Print code authentication using the Modify option.
  • For more information on adding printers, refer to CPA Manager. For prerequisites and supported printers, refer to CPA 2.0 and its sub-topics.

Confirm the Web Print Portal and feature are working:

1. Select the portal link in the Web Print section.
2. Verify the portal loads and that your organization logo appears.
3. Authenticate to the portal:
   1. If you enabled Allow Authentication, confirm that the sign-in prompt appears.
   2. If you enabled Allow Guests, select Continue as Guest and enter an email.
3. Upload a test document in a supported format and select Next.
4. On the Print Preview page, select the desired printer and adjust print job settings as needed.
5. Select Print.

Without Secure Release Print or guest printing turned on, the job prints immediately to the selected printer.

With Secure Release Print or guest printing turned on:

1. Select Print Now to test directly printing.

Additionally, repeat the process above, but select Hold after selecting Print.

Authenticated Users

Release the job using one of the following methods:

Guests