Comment 3 for bug 885743

We're on 3.3.4 and, due to major overhaul of staff permissions for the consortium, have discovered some staff accounts created by local System Admins have been logging into the web staff client for weeks without any working locations assigned and able to perform multiple functions without them. It is only some activities that seem to check for valid working locations with no notification that the failure (to create a new volume or item, for example) is because no working locations assigned for that branch.

In the past, staff could not log in via XUL without a working location assigned for the branch they were selecting as their workstation. It seems that the web staff client should perform that same check and it would certainly be helpful when a check is performed to add error messages that indicate a function could not be completed because account does not have necessary working location assigned while performing tasks in the web staff client. Not sure how big an ask that is though. :)