There is no way to remove the user from the process. Because we use single sign on a user can access multiple communities with their username and password it would create a huge security vulnerability if passwords could be reset without a users consent.

I agree that Administrators should have more control over community member accounts.  For Social Networks, I can understand why this is limited; however, for Business Networks administrators should have the ability to create accounts, reset passwords, change member profile information, etc. - as well as the ability to lock these things down so that members cannot change them.

Igloo made a great step in this direction recently by allowing the ability for Administrators to "Add Members" from the Control Panel\Manage Members area.  This allows an admin to create the accounts in advance.  However, once you "turn over" that account to the member, they can modify all of their information, including changing of their password (which is actually a good thing).  But what if an admin needs to go in an change some profile info for a member, or perhaps subscribe them to new forum(s)?  He/She must ask for the member's password, login as them, make the change and then tell the member to change their password again.

I would recommend a model similar to Moodle's, whereby the admin has complete control over the member's account, but also allow the ability to force password change upon next login.  I find this to be a very useful model.  Furthermore, if the member forgets their password, it is easy to go in and change the password, provide the access and then force a password change upon login.

While I understand that José is asking for this capability in the API, I would suggest that the same functionality and control be provided through the Manage Members interface as well.

@Bryan - Seems we were posting at the same time :)

I see your point about the SSO with logons across communities, and understand how this complicates things. Let me think about this one some more as I was only considering a one-dimensional approach to this problem.

I agree with both Jose and Paul. In the scenario of a closed business site, it makes a lot of sense. With IGLOO broadening their target audiences, you also need to expand functionality for new use cases!

@Michael

Me too !