Leap Access and Staff User Permissions Checking in Leap

Leap access is controlled using permissions in Polaris Administration. You can also control whether Leap can be accessed from workstations in the library network.

The Access Leap: Allow permission must be granted to all staff members who will be using Leap. The Access Leap remotely: Allow permission is used to control access to Leap outside of the library system's network. These permissions are not granted by default.

If your library wants to limit who can access Leap remotely, two Leap web applications must be set up on the same or different servers. One will be used for staff accessing Leap through the library's network with restrictions based on the library's internal IP address. The second Leap web application will be set up to accept all connections, but access will be granted only if the staff member has the permission Access Leap remotely: Allow.

Two URIs are required if your library wants to restrict remote access, for example:

https://mylib.org/leapwebapp

https://mylib.org/leapwebappexternal

Note:
If your library plans to restrict access to Leap depending on the staff member's location, contact your Polaris support representative.

User permissions are checked according to settings in Polaris Administration. For example, if a user has the permission to register patrons in the Polaris staff client, she will be able to register patrons in Leap. In addition, the following Cataloging permissions are required to work with item and bibliographic records in Leap:

• To access item records in Leap, the following permissions are required:

  • Access cataloging subsystem: Allow
  • Item record: Access
• To access bibliographic records in Leap, the following permissions are required:
  • Access cataloging subsystem: Allow
  • Bibliographic Record: Access
• To modify item records in Leap, the following permissions are required:
  • Item records: Access
  • Item records: Modify cataloging view. In Leap, this permission applies to the Controls view.
  • Item records: Modify header. In Leap, this permission applies to the Details view.
  • Item records: Modify notes and notices view. In Leap, this permission applies to the Blocks and Notes view; Notices is a separate view that cannot be edited.
  • Item records: Modify source and acquisition view. In Leap, this permission applies to the Source and Donor view.
• To create item records in Leap, the following permissions are required:
  • Item records: Create
  • Item templates: Access
• To delete and undelete item records in Leap, the following permissions are required:
  • Item records: Delete/Undelete
• To delete and undelete bibliographic records in Leap, the following permissions are required:
  • Bibliographic records: Delete/Undelete
• To delete and undelete authority records in Leap, the following permissions are required:
  • Authority records: Delete/Undelete

In general, when users perform a task in Leap, permissions are checked in the same way as they are for the equivalent task in the Polaris ILS. However, for the following tasks, permissions checking is different in Leap:

• Modify patron accounts - In the Polaris ILS, if a staff member does not have permission to modify patron accounts, no override is available. In Leap, authorized users can override the permission block if a staff member does not have permission to modify patron accounts.
• Access the patron workform - In Leap, the patron workform contains both registration and status information, so the user must have at least Patron status: Access or Patron Registration: Access permissions to access the patron workform.
• Find Tool patron search - When a staff member scans a patron’s barcode or searches for a patron record, and the staff member does not have permission to access that patron’s record, a message indicates that the barcode was found, but that the record cannot be opened because the staff member does not have the required permissions. The patron record can be opened for checkouts only.
• Override permission blocks - When a staff member has insufficient permissions to do a task in Leap, an Override box lists all the permissions the staff member lacks. A staff member with the Override permission can enter their credentials to override the permissions checking and allow the user to continue with the task. The override will continue in effect for the user’s logged in session, unless the override is cleared.
• Picklist - The Picklist application permissions apply only to the Leap Picklist. To use the Picklist, the Picklist application: Allow permission is required. To change the circulation status from the Picklist, the Picklist application: Modify circulation status permission is required.