<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-family:"Calibri","sans-serif";
        mso-fareast-language:EN-US;}
@page WordSection1
        {size:612.0pt 792.0pt;
        margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=NL-BE link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Earnie,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I think you still can use og, but only use it for the user management not for the posts. Just create a dummy node type (my_people) so admins can add, edit, remove users.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Other solution would be to add a profile field (admin only) and use it to store the creating user. Afterwards build a view that only show those users and use hooks to double check when editing<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Good luck,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Peter<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><a name="_MailEndCompose"><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></a></p><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> development-bounces@drupal.org [mailto:development-bounces@drupal.org] <b>On Behalf Of </b>sivaji j.g<br><b>Sent:</b> zaterdag 4 september 2010 1:33 PM<br><b>To:</b> development@drupal.org<br><b>Subject:</b> Re: [development] [support] Administer a subset of users<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><div><p class=MsoNormal>On Wed, Sep 1, 2010 at 5:02 PM, Earnie Boyd <<a href="mailto:earnie@users.sourceforge.net">earnie@users.sourceforge.net</a>> wrote:<o:p></o:p></p><div><div><p class=MsoNormal>sivaji j.g wrote:<o:p></o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'>Hi,<br><br>I am developing a smart school site where one of the user roles is<br>"collage". Users belongs to this role need to be allowed to administer a<br>subset of users "students" in the site. The subset of users can be the<br>users in OG group. The group admin need to be allowed to create, edit,<br>block and delete users in the group context.<br><br><br><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></div><p class=MsoNormal><a href="http://drupal.org/project/og" target="_blank">http://drupal.org/project/og</a><o:p></o:p></p><div><p class=MsoNormal style='margin-bottom:12.0pt'><br>OG module will not fit here. I am sorry if it is not explained clearly. What i would need is a way to allow some of the site users to create/ mange their own sibling user account. I know Drupal core doesn't handles this case and there is no contrib module for the same. <br><br>A similar requirement is clearly explained here in d.o forum <a href="http://drupal.org/node/696664">http://drupal.org/node/696664</a><br><forum-snip><br>Our users are customers and they must be added by an administrator. Some customers should be enabled to create their own "subcustomers" and of course be able to edit and delete them.<br>The problem is, that if you want to enable someone to add users, by default, there is only the "administer users" permission. They would have been enabled to edit all other customers as well with that permission. Of course, you could protect your users with the user_protect module or others, but then, the "customer admins" would not be able to edit their own subcustomers any more.<br></forum-snip><br><br>I posted this here to get core developer attention to see if there are any discussions going on to introduce this feature, unfortunately nobody has experienced similar requirement or reluctant to share their approach. <br><br>The possible best solution recommended to me is to expose a version of the registration form to create sibling users. Hope this will help others.<br><br><o:p></o:p></p></div></div><p class=MsoNormal style='margin-bottom:12.0pt'><br><br><br clear=all><br>-- <br>Sivaji<br><br><br><o:p></o:p></p></div></body></html>