Yes. Users can submit print jobs to either printers or pull printers provided they have been authorized to use them. Pull print jobs are released at the print device using a mobile app or a release page in a mobile browser.

Yes. The username and document names in all records for a given user can be redacted on demand.

Yes. A complete job history can be viewed by the Administrator, and all users can view their own job history. Reports are also available.

Print job data can be "aged out" of the system after a configurable period of time (default: 12 months).

Not currently. To print using LRS CloudPrint, the user must be able to log in to the Azure^® Active Directory belonging to the tenant organization. There is currently no support for guest users from outside the Azure Active Directory.

Not currently. The user can direct a print job either directly to a nominated printer or to a pull printer, which allows the release of the job on any printer device associated with that pull printer. The pull print job is released by scanning a QR code attached to the printer and then selecting the job for release using a mobile app or a mobile release web page.

When you sign up, you can choose where you want your data to be stored. Current choices are "Western Europe" or "Central US". In general, we find that companies like to have their data where the headquarters are based. There is currently no migration service from one region to another.

We don't offer support for specific brands, though we do test across a wide spectrum of vendors. If your device supports IPP/IPPS and has a WHCL-signed driver for Windows, or for macOS, has either a packaged driver or supports IPP-Everywhere, then it will work with LRS CloudPrint. For mobile printing it needs to be able to print native PDF.

LRS CloudPrint does not bundle any drivers as standard, the customer uploads their own drivers. The reasons for this are that the customer knows best when it comes to drivers and generally wants to use those drivers with which his users are familiar. Also, the administrator can update drivers whenever he wants or needs to without worrying about breaking any "standard" driver provision.

If your driver allows pre-configuration before it is uploaded into LRS CloudPrint then yes, provided the pre-configuration does not break the WHCL signing on the driver. Default configurations can be added to drivers within LRS CloudPrint, and the correct default configuration chosen for deployment for any defined printer.

If a Windows® driver is WHCL-signed, or a Mac® driver is packaged in a standard format, then generally speaking it can be uploaded into LRS CloudPrint for use with printers. For Windows, most self-extracting archive and Zip formats are supported, but occasionally we encounter a package which can't be unpacked in the cloud following upload.  In that case, a clear message is displayed and instructions are provided in the on-line documentation for extracting and re-packaging 'difficult' drivers.

Both of these options are available in LRS CloudPrint. Cloud Tunnel printing can be enabled, which allows administrators to define printers whose jobs will all be sent via the cloud. By default, all jobs are retained at the originating client and dispatched from there at print time.

No - mobile print jobs all travel via the cloud and are all dispatched via the LRS Notification Hub in the cloud, the mobile user only needs a cloud connection, be it via the company network or other internet connection. All mobile print submission traffic is encrypted, guaranteeing security.

LRS CloudPrint provides reporting on jobs by User, Printer and Device over a selectable date range, with some simple charts and the capability to export any viewable report to Excel. We plan on adding further reports in the future.

Yes, printers can be auto-deployed based on the group memberships of the logged-in user at the client.

Yes. The overall period for retention of a tenant's data following completion of a print job can be set by the Service Owner. The default is 12 months, which is also the maximum data retention period. All data can be exported by the tenant at any time should they wish to keep data for longer periods locally.

All individual job records are deleted. Some statistics are retained in case billing questions arise later. These statistics contain no references to individual users or print jobs.

This is not currently a feature of LRS CloudPrint.

Yes, LRS CloudPrint enables administrators to run reports of all the data held which contains personally identifiable data.

Yes, with LRS CloudPrint you can make all data unidentifiable on demand.