First off, let me say that this will work, but I've never done it in a production environment. There may be a better way, but this is the first solution I came up with. Second, let me say that you need to understand and accept this caution: if not managed correctly, you could give EVERYONE read/WRITE ACCESS to ALL user ACCOUNTS. But, if you're still interested, here's my solution...

Open the database and go to the DesktopModules table. Find the row with the FriendlyName of User Accounts - mine has an ID of 13. Change the IsAdmin column of that row to 0. This will allow you to see it in your modules list in the control panel. From here, you add it to any page as you would any other module - just be careful about managing permissions. Immediately after adding it to the page you want, I suggest going back and changing the IsAdmin column back to 1. This will ensure nobody accidentally adds the module to another page with less restrictive permissions.

This should do ya! I can't say it enough, tho... BE CAREFUL when setting permissions for this. If not done right, you could essentially give the world access to delete all users (except for the host account, that is).

---

Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com

No, I have not tested it. Your post sparked an interest and I just had to figure it out I was actually looking at a different way to implement it, but after looking at a few things, that seemed to be the easiest implementation. Think about it, tho, you really only have two options: create your own module or use the existing admin module. Either way, you're getting into risky territory because one slip in permissions could give everyone access to manage everybody. Simply giving this capability to non-admins is dangerous, in and of itself. I honestly don't think this approach is better/worse than any others overall. I'd be interested in other methods, tho, just out of curiosity.

---

Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com