Hi Randy, I am afraid it is by design ;) The reasoning behind this is that we are encouraging a distributed management of users.
The rule is that a user can only see another user in the user list if he - has all of the authorities of that user (inherited through the user roles) - is at a level above or at the same org unit in the org unit hierarchy This way we are able to let e.g. district users create, update and otherwise manage facility users. In a large country this is an effective way of properly managing users as we have seen in Kenya. If users could create other users with authorities they don't have themselves they could effectively shortcut the whole authorization setup. The downside is obviously that it becomes hard to create such a national help-desk team you describe. I guess the only solution at the moment is to give the help desk user role all the authorities of which they should be able to grant others. regards, Lars On Wed, Feb 22, 2012 at 10:29 AM, Wilson,Randy <[email protected]> wrote: > I'm creating a user role called Helpdesk in DHIS 2.6 and their role is simply > to add accounts and reset user passwords. > > I've assigned them every function with user in it (Add, list, delete) users, > user groups, user roles. > > When I create a user and assign them to this role at the national level, they > are able to login and navigate to the user maintenance module and they can > create users, but they cannot see the list of users if they want to reset > passwords. > > Is this a bug or by design? > > Randy Wilson > HMIS Advisor/MOH Rwanda > > _______________________________________________ > Mailing list: https://launchpad.net/~dhis2-users > Post to : [email protected] > Unsubscribe : https://launchpad.net/~dhis2-users > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~dhis2-users Post to : [email protected] Unsubscribe : https://launchpad.net/~dhis2-users More help : https://help.launchpad.net/ListHelp
