Printing in Silo is like printing from a local browser with a few additional options, including the ability to set specific policies to enable or restrict printing.
- Silo must be installed
- A connection to a printer
- Policy enabling print
How to Print
1. Open the Silo Context menu, select the Print button. This will render the PDF document in the Silo tab, and will give you the ability to format document parameters, like orientation, paper size, magnification, etc. Once these changes are made, the print file is created and delivered to the computer.
This pop-up box appears.
3. Next, the Print confirmation window appears. Select the Print button.
Note: If you use Ctrl + P, the Silo Print window does not appear. See Printing with Windows below.
Printing with Windows
Silo downloads the page(s) and then will launch an external PDF application to view and print the pages. Windows users will need to have a supported PDF reader to work. Supported readers:
Adobe Acrobat Pro
Adobe Acrobat Readers
Nuance Power PDF Advanced 126.96.36.199
New with Windows 2.9.12, from the login window, click the Gear button, the "Print" selection provides an improved PDF printing solution. The default option, Use Silo, leverages a robust, reliable open-source PDF library, PDFium, to view, search, and print PDF files. You may choose this or one of the external applications listed above.
The print window has an updated look, too.
The Windows print window:
Printing with Mac OS X
Silo uses the native OS X printing API to have the client display a print dialog and print from the client app.
Using the Printing Policy
The printing policy is listed in the admin console policy panel in the Data Transfer section:
The print policy allows you to enable, block, or enable print from any device.
It is important to understand how data is processed during printing, and how the printing policy may conflict with your data download policies. When printing, Silo will render the data as a print file and automatically pass the file to a /temp directory. This file is deleted at session close.
If your compliance process requires a zero-residue policy, keep printing policies set to OFF. While the print file is deleted from /temp at session close, there may be conditions - either explicit or through client-side exploit, where this data may be copied and saved elsewhere or recovered in a forensic process. Any scenario where the print file is recovered may undermine your zero-data-on-the-client policy.
Similarly, if you set your print policy to block, but allow data download, then a user would be able to download a copy of the data and print locally.
Please contact Support if you have any additional questions and/or require further information.