22-1 Levels of access and control

Chapter 2: Preparing for ColorPASS Setup

To prepare for printing at your site, you need to do some initial ColorPASS

configuration, or Setup, to specify the network environment and the kind of printing you will do. Before you perform Setup, you must decide the levels of access you will implement for your site. Administrators and operators must also understand how ColorPASS system software is structured in order to configure and use the ColorPASS system correctly.

Levels of access and control

When you configure the ColorPASS during Setup, you (as system administrator) implement a particular level of control by enabling or not enabling print connections, passwords, and access to Fiery WebTools. The level of control you implement can range from strict to moderate to minimal—or none at all.

•Strictest control might be appropriate for a high-volume printing environment where an administrator or operator controls the job flow and all printing; jobs sent by users are spooled (stored) to the ColorPASS disk until the operator decides it is time to print them. In addition, only the administrator and/or operator have access to job management tools.

NOTE: The term “job management tools” is used in this manual to refer to the Command WorkStation, Fiery Spooler, and Fiery WebSpooler.

•Least control might be appropriate for a small site where anyone on the local network can control all printing and ColorPASS functions. Although there may be an administrator or operator charged with certain duties, all users have equal access to the system and job management tools.

ColorPASS print connections

The ColorPASS supports three print connections: Hold queue, Print queue, and Direct connection. These print connections can be enabled, or “published,” to users on the network when you configure Printer Setup. All published connections are constantly checked for the presence of jobs. The Print queue and the Direct connection give remote users more direct access to the ColorPASS than the Hold queue. Therefore, do not publish the Print queue and the Direct connection in environments where stricter control is desired.