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.
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.