After further testing, it seems the problem relates to the number of work
locations I assigned. I was assigning every branch library (170 locations
in our instance) to each of the network staff. When I only assigned one
branch location, then the org units display properly.
It seems to me that ne
That seems to be the problem but there is a twist. In setting up the user
accounts I ran the following SQL statment to automatically assign all of our
branch locations to network staff.
insert into "permission"."usr_work_ou_map" (usr, work_ou) SELECT 15, id
FROM actor.org_unit WHERE ou_type=4
W
Aha, that sounds correct.
Have you checked to make sure that you've granted working locations for
the network staff accounts for the workstations they're logging in from?
-- Ben
On 03/21/2011 11:05 AM, Tim Spindler wrote:
> Thanks Ben, I'm confused then because I have
>>
>> * group_applicat
Thanks Ben, I'm confused then because I have
- group_application.user
- group_application.user.patron
At the STAFF level and I assumed that it would cascade down for the groups
underneath staff (ACADEMIC, PUBLIC, and NETWORK). I don't have anything
additional on the public staff and they
Hi Tim,
Looking at the permissions, I think you have to add one for the network
staff for general all users: group_application.user
If they don't have that, they won't be able to create any user who's a
child of the primary users group (i.e. every other group).
Probably also need to have group_
I'm not sure if this is a bug or the way I have something set up but I'm
looking for Advice. I have a situation where public library staff can
register patrons and the local admin can set up accounts for their library
fine. Howver, none of the network staff can create user accounts because the
org
