Well its certainly possible to do that in code but I have no plans to implement such a feature so you would need to do that yourself if you really need it. My goal has been to ensure that the sites are completely separate in terms of users. I don't want to build any security holes in that model.

I think there is already a feature to filter specific users from the member list, if not I would be willing to implement that so that the admin users could be unlisted.

I've been working on a feature for a client that might be of interest to you though and might allow you to approach theyour goal from a different angle. It allows creating visual sub sites that have their own skins and look like independent sites but they share the same users with the parent site because it is really just the same site but with section home pages that show only the pages beneath the section in the menu(s). The member list is not filtered though since it really is all one site.

My clients needs are top level

University Site
--School of Foo (Section Home)
--School of Bar (Section home)
--School of Music (Section home)

with each section having its own skin and logo and menu. In fact each section home has a split menu skins with a top horizntal menu showing sub sections within the section and child pages below the sub section shown in a left vertical menu

The logo, home link etc all point to the section home rather than the root site home.

I haven't created the officla documentation yet, but its in svn and these are the notes I sent my client for testing:

1. Create the page hierarchy something along these lines
University of Music (main root site)
--School of Jazz ( apparently a separate site) (siteRoot/schoolofjazz.aspx)
----Swing Department (section of sub site) (in split menu this would
be the top menu)
------Some page 1 (in split menu this will be the top level of the
left menu when
-------- ... more pages later

Create a custom skin for the School Of Jazz by copying one of the
split menu skins like treeview2. Set that page to use this skin, then
in the layout.master file
1. edit the home link so it points to the School of Jazz page like this:

<portal:HomeLink id="HomeLink" runat="server"
OverrideUrl="~/schoolofjazz.aspx" />

2. edit the site logo so it links to the Schol Of Jazz page and use
its own logo if desired.

<portal:SiteLogo id="SiteLogo" runat="server"
OverrideUrl="~/schoolofjazz.aspx"
OverrideImageUrl="~/Data/Sites/1/logos/mojotonguesmall.gif"></portal:SiteLogo>

3. edit the site title like this:

<portal:SiteTitle id="SiteTitle" runat="server"
OverrideUrl="~/schoolofjazz.aspx" OverrideTitle="School of
Jazz"></portal:SiteTitle>

4. Set the StartingNodeOffset=1 on the top SiteMenu, this makes the
top menu bind to node beneath School of Jazz

<portal:SiteMenu id="SiteMenu1" runat="server"
UseTreeView="false"
TopLevelOnly="true"
StartingNodeOffset="1"
Direction="Horizontal">
</portal:SiteMenu>

5. On the page menu set StartingNodeOffset=2

<portal:PageMenu id="PageMenu1" runat="server" UseTreeView="true"
StartingNodeOffset="2" />

New pages created below School of Jazz should automatically get the
same skin as the School of Jazz page.

Joe

1. You can do it in code. Its just a matter of assigning the user the siteid by passing in SiteSettings to the constructor.

2. When I get to more work on the Site Office feature I will implement user groups which can be used to filter users. In practice these groups may correspond to roles, but I just don't think it would be wise to use roles directly for this as I don't think it is wise to enumerate the roles for visitors.

4. Yes if you are looking for code example, look in the mojoPortal.Business.WebHelpers.mojoSetup.cs. When a new site is created from Site Settings, it creates an admin user for the site and adds him to the Admins role

Joe