2022.2

Table Of Contents
Preferences button under the PlanetPress Workflow (W) button, or via the key combination
Ctrl+Alt+P .
Network considerations
While PlanetPress Workflow is typically installed on a server machine that is only accessed by one
single user such as an IT person, multiple users logging on to that machine is a possibility (except with
terminal servers, see "Environment considerations" on page18). Because each user may have dif-
ferent local and network rights, it may be important to consider the implications in regards to Plan-
etPress Workflow. To change the service log on information, see "Workflow Services" on page285.
Local and network rights
Programs, such as PlanetPress Workflow and all its services, must identify themselves in order to be
granted permission to perform operations on the computer on which they run as well as on other com-
puters accessible via a network connection. On a given workstation, you can configure your Plan-
etPress Workflow to use either the local system account or any specific user account. When you do
this, you grant PlanetPress Workflow and all its services the same rights associated with the selected
account.
When you are running PlanetPress Workflow Configuration program on a workstation, if it is associated
with an account that is different from your account, the following icon is displayed in the lower right
corner of PlanetPress Workflow Configuration program: . The icon reminds you that the logon inform-
ation is different for the PlanetPress Workflow services, and that some network resources may not be
accessibly by PlanetPress Workflow when running a live configuration.
Account requirements
PlanetPress Workflow and its services require administrator rights to run on any given computer and
must therefore be associated with an account that has such rights.
We recommend creating a network or domain account specifically for the PlanetPress Workflow ser-
vices, which has administrator credentials on the machine where it is installed, and is given proper
rights for any network resources your configuration may request.
Mapped drives
It is strongly recommended to use local folders instead of mapped drives whenever possible.
Mapped drives (for example, drive X: leading to \\server\public\) are always user-specific and are cre-
ated at logon. This means that mapped drives are typically not available to the PlanetPress Workflow
services when running a live configuration.
Furthermore, while the mapped drives are not shared, they are still limited to one map per computer,
meaning if one user maps the X: drive, a different user (or a service) will not be able to map it again.
This creates a limitation in PlanetPress Workflow: if you create a mapped drive as a user, you will not
Page 25