Under the permissions tab of a local connection you can set up permission set rules and options, and also define rules for suspending a user's access based on attributes passed by the local source - e.g. the patronStatusInfo.statusType attribute from a Sirsi system.

You can base the rule on any attribute or combination of attributes supplied by your local system. Just as with the permission set rules, the attributes need only be passed, they do not have to be otherwise mapped.

Accounts that match the suspend rules will not allow access to resources and are shown in the account list as suspended.

  1. Click the add suspend rule button

  2. Give it a name

  3. In the 'When' area:

    1. Enter the name of the attribute in your local source. Attribute names are case sensitive.

    2. Select your condition, e.g. contains, starts with

    3. Enter your comparison

    4. If you need to add other conditions, add additional lines with the plus button and specify if any or all conditions must be met as appropriate. You can add as many lines as you need to.

  4. When happy, click done and set up any other rules. You can create as many rules as you need to.

  5. Use the save button when done and subsequent logins will use these new rules. (The save button is hidden whilst you are adding or editing rules)


If you wanted to suspend access for users when memberOf contains Visitor OR when memberOf contains walk-in you would specify both conditions and select when any conditions are met.

If you wanted to suspend access only when memberOf contains Staff AND when memberOf contains Teaching you would specify both conditions and select when all conditions are met.

If you wanted to suspend access when users did not have specific attribute values, you would use all - e.g. OU does not match Physics_Department AND OU does not match Chemistry_Department.

Multi-valued attributes