Currently, the ability to override a hold block is governed by permission 92.

A hold might be blocked for a number of reasons. Staff might attempt to place more than the max number of holds allowed for a customer. They might place a hold for a customer on an item they already have checked out, etc.

One scenario especially has been problematic for as long as I can remember:

A patron finds an item on the shelf & takes it to a service point to check out. It turns out that this item can satisfy a hold placed by another patron. The Sierra client displays the message:

Message
Item on hold for another patron .p<xxxxxxx>. Check out item anyway?

Alternatively, we see situations where a patron sees an item on a shelf that they want & takes it to the service point to be checked out. In this case, they just happened to pull it from the hold shelf, where it was already awaiting pickup by another patron. Here, the Sierra client will display this message:

Item on holdshelf for another patron .p<xxxxxxx>. Check out item anyway?

We would really like the ability to allow the first circumstance & prevent the second, across the board, which would mean separate permissions for each, one that we'd assign to staff & one that we'd deny.