Microsoft Office Tutorials and References
In Depth Information
Then, for each zone, if you click its name, you can edit the settings (the same ones you saw
during creation—enabling anonymous, setting up Windows authentication to use NTLM, and
so on. See Figure 10.45.
settings for the
Self-Service Site Creation
With all these different sites and all the possible templates and site definitions, you could easily
find yourself doing nothing all day but creating the following new subsites: new meetings, new
blogs, new document workspaces, and so on. You might be tempted to give more users Create
Subsites permissions so they can create their own subsites. Of course, then you’ll have the
nightmare of all these subsites popping up with no organization, and you’ll need to deal with them
(keep in mind that each subsite eats into the site collection’s storage quota, if there is one).
As an alternative to letting your users create subsites on your main site collection, you can
enable self-service site creation. Self-service site creation allows users (and not just farm
administrators) to create their own site collections. Then you can more easily apply a storage quota to
each of their site collections (they’ll probably only ever use the top-level site) and apply the
automated deletion feature (under Site Use Confirmation And Deletion) that can be used to delete
unused site collections.
DOES ALLOWING USERS TO CREATE SITE COLLECTIONS GIVE YOU CHILLS?
Of course, giving users the right to create their own site collections (instead of creating subsites)
presents its own problems. Site collections are easier to manage from Central Administration, but
they are fully functional site collections, with a top-level site, the capacity to have many subsites of
all kinds, and their own users and permissions. So, there is a trade-off: ease of management versus
giving users carte blanche over their own collection of sites.