Skip to content
SubClik

SubClik Print · How it works

From install to the first release in an afternoon.

One program at the site, one portal for the office, and the queue added to computers by the tools your IT team already uses.

Download the print serverTry the demo

Seven steps

  1. 01

    Install the print server

    On a Windows, Mac or Linux computer at the site that stays on: the school’s server, an office PC or Mac, or a small Linux box. One program, no database to install. Download it here.

  2. 02

    Pair it with your organisation

    In the SubClik Print portal, add the site and create a pairing code. Run the pair command once and install the service; from then on the server takes its set-up from the portal.

    subclik-print pair ABCD-EFGH
subclik-print install
subclik-print start
  3. 03

    Add the machines

    Name each copier or printer, its location and its network address. Choose which machines a job may move to if this one breaks down, usually the nearest ones on the same floor.

  4. 04

    Add the queue to every computer

    The secure queue is an ordinary IPP printer, so no driver has to be rolled out. Windows uses its own Microsoft IPP Class Driver; push it with Intune or Group Policy:

    Windows (PowerShell, Intune or Group Policy)

    Add-Printer -Name "SubClik Secure" -IppURL "http://print-server:8631/ipp/print/SubClik%20Secure"

    macOS: add an IPP printer, or deploy the same address by profile. ChromeOS: add it as a print server in Google Admin.

    ipp://print-server:8631/ipp/print/SubClik%20Secure
  5. 05

    Bring people in

    Connect Microsoft Entra ID or Google Workspace and people stay in step on their own, or add them by hand or from a spreadsheet. Set PINs, quotas and colour rules per person or department. Cards are registered by tapping them at a machine.

  6. 06

    Print and release

    People print as usual, to SubClik Secure. At any machine they tap a card, type a PIN or scan the QR code with their phone, pick their documents and print. Jobs nobody collects are deleted after the hold time (12 hours unless you change it).

  7. 07

    Scan

    Set each copier’s SMTP server to the print server on port 2525. Scans to name@your-scan-domain go to the person; scans to folder-key@your-scan-domain go to that folder. OneDrive, SharePoint, Google Drive and Dropbox work once the account is connected in the portal.

What happens to one document.

A teacher prints a worksheet in the classroom and collects it in the staff room.

  1. 1

    Printed. Windows sends the PDF to the SubClik Secure queue with the teacher’s sign-in name. It waits on the print server, not on any copier.

  2. 2

    Signed in. At the staff-room copier the teacher taps their card. The screen lists their documents and the pages left this month.

  3. 3

    Checked. Before sending, the server asks the copier for its state. It has a paper jam, so nothing is sent and the screen offers the office and library machines.

  4. 4

    Released. The teacher picks the office machine. The job goes there by IPP, the server follows it until the machine reports it printed, then deletes the document.

  5. 5

    Recorded. The job, its pages, colour and machine go to the portal for quotas and reports. Document names can be hidden for privacy.

For the IT team: network

Everything stays on the site’s network except one outbound HTTPS connection to the portal.

Network connections used by SubClik Print
ConnectionPort
Computers, tablets and phones → print serverPrint queues (IPP) and the release screenTCP 8631
Copiers → print serverScans (scan to email)TCP 2525
Print server → machinesSending jobs (IPP or raw) and reading machine status (SNMP)TCP 631 / 9100, UDP 161
Print server → SubClik portalSet-up, reports and cloud scan uploads. Nothing connects in.TCP 443 outbound

Questions

What does the print server need?
A 64-bit Windows 10 or 11, Windows Server 2016 or later, or a Linux computer with systemd, on the same network as the machines, that stays on during the day. Disk space for the documents waiting to be collected; they are deleted after printing or after the hold time.
What if the internet goes down?
Printing and release carry on. The server keeps its last copy of the set-up from the portal, and sends the job history when the connection is back.
Do shared computers work?
Yes. Each job carries the name of the person signed in to the computer, so five teachers on one classroom PC each get their own jobs. Other sign-in names a person uses (DOMAIN\name, name@school.org) are added as aliases.
Can people release from a phone?
Yes. Each machine has a QR code; scanning it opens the release screen for that machine in the phone’s browser, on the school’s Wi-Fi. No app to install.
Several buildings?
Install a print server in each building and pair each one with its own site. People, cards, PINs and quotas are shared across the organisation.

See the portal with a school’s sample set-up.

Sites, machines, queues, people, quotas and print history are ready in your own demo.

Open the demo