Access ControlConfigure a Job Target Folder

Status information about print jobs is stored in a job target folder. For print jobs processed by using an integration, you must specify a unique job target folder when you configure the integration. On-demand print jobs use the built-in Job Target folder provided with Loftware Enterprise™ SP, which can be renamed but cannot be deleted.

You must create and specify a different job target folder for each integration. It is suggested that you create subfolders in the built-in Job Target folder to serve as the job target folders for each integration.

Note: Although the object access permissionsClosed Permissions in Loftware associated with a specific object or with a folder that control what actions can be performed on that object or on objects within that folder. Each object has default permissions that can be overridden by exceptions for a specific group or user. A user must have both a role-based permission and the corresponding object access permission to perform an action on an object. of a folder can be inherited by subfolders, subscribing to a job target folder provides you only with status information for jobs associated with that specific job target folder and does not include information from any of its subfolders.

To configure a job target folder for an integration, do the following.

  1. In Access Control Access Control, select the folder in which you want to create a folder to serve as a job target folder.

    Tip: It is suggested that you create subfolders in the built-in Job Target folder to serve as the job target folders for each integration.

  2. In the ribbon Home tab, click Folder in the Create group.
  3. Configure the options in the Create Folder dialog box, and then click Save. For more information, see Create a Folder.

    Important: You must specify a separate job target folder for each integration.

  4. Grant object access permissions to at least the Run As user for the integration. You can grant these permissions to the group that you created for Run As users or make them the Default Permissions for the folder if preferred. Grant at least the following object access permissions: Read, Create, Delete, and Print permissions for Jobs; Read and List permissions for Folders; Read and Queue permissions for Device Groups.

    Tip: To grant permissions only to the group that you created for Run As users or only to the Run As user for a particular integration, add that group or user to the Group Permissions or User Permissions table.

  5. Type Read Write Create Delete Admin List Print Design Print Publish Reprint Queue
    Folders Granted Inherited Inherited Inherited Inherited Granted
    Users Inherited Inherited Inherited Inherited Inherited
    Groups Inherited Inherited Inherited Inherited Inherited
    Roles Inherited Inherited Inherited Inherited Inherited
    Documents Inherited Inherited Inherited Inherited Inherited Inherited Inherited Inherited Inherited
    Device Groups Granted Inherited Inherited Inherited Inherited Inherited Inherited Inherited Granted
    Servers Inherited Inherited Inherited Inherited Inherited Inherited
    Jobs Granted Inherited Granted Granted Inherited Granted Inherit Inherited
    Processes Inherited Inherited Inherited Inherited Inherited Inherited Inherited Inherited
    Integrations Inherited Inherited Inherited Inherited Inherited Inherited
    Data Services Inherited Inherited Inherited Inherited Inherited Inherited Inherited Inherited
    User Profiles Inherited Inherited Inherited Inherited Inherited
    Remote Sites Inherited Inherited Inherited Inherited Inherited
    Facilities Inherited Inherited Inherited Inherited Inherited
  6. Click Save .