Turns out REGISTER_WORKSTATION is set to Consortium in the Concerto data set. I changed it to Branch on the test server and the user is now only able to register a workstation to the branch(es) that match their working location(s).
STAFF_LOGIN is also set to Consortium which explains users logging into other branches. When I switched STAFF_LOGIN to System or Branch login stopped working for everyone except global admins. On our 2.10 training server we have STAFF_LOGIN set to Consortium. I tested changing it to Library and login stopped working there as well. So I think this is normal.
One other peculiarity I ran into, that may be by design, is that Global Admins can delete all workstations and then use the client without a registered workstation. Other users cannot delete (Remove) the workstation they are currently logged in with.
Turns out REGISTER_ WORKSTATION is set to Consortium in the Concerto data set. I changed it to Branch on the test server and the user is now only able to register a workstation to the branch(es) that match their working location(s).
STAFF_LOGIN is also set to Consortium which explains users logging into other branches. When I switched STAFF_LOGIN to System or Branch login stopped working for everyone except global admins. On our 2.10 training server we have STAFF_LOGIN set to Consortium. I tested changing it to Library and login stopped working there as well. So I think this is normal.
One other peculiarity I ran into, that may be by design, is that Global Admins can delete all workstations and then use the client without a registered workstation. Other users cannot delete (Remove) the workstation they are currently logged in with.