Microsoft Office Tutorials and References
In Depth Information
E N A B L I N G S E L F -S E R V I C E S I T E C R E A T I O N
The web application in this case was created so that users could have their own blogs, complete
with a root site collection (this site collection becomes important when self-service site creation
is enabled). There are basically two ways of going about allowing users to create their own blog
site: allow them to create subsites in one site collection or enable self-service site creation. They
both have their pros and cons.
If you allow users to create subsites in a site collection, they can create as many as they want
there. That’s because when you enable the permission, there is no inherent limit to how many
they can create. But they at least can only overload one site collection.
On the plus side, that one site collection with all the subsites is pretty easy to back up and
restore. Also, users don’t need to know how to manage their own security if they simply inherit
the settings from the parent site. They also can use any custom templates you may have added
to the site collection. On the other hand, if you have users abusing the permission to create
subsites, you will have to track down the subsites they create and delete them manually. Also, the
site collection quota will affect all the subsites in the collection, meaning that one person’s
overloaded subsite can lock the site collection for everyone.
If you enable self-service site creation, yes, the users can create their own site collections
(with their own users and security). In fact, they can create as many as they want (once enabled,
there is no way to limit how many site collections the users can create), and that’s pretty
powerful. But you can also set up usage notification and automatic deletion, which will automate the
deletion process, freeing you from having to hunt down and delete unused site collections
yourself. Also, each site collection will have its own storage quota, so no one will be locking anyone
else’s sites with their data overload (they will be limited by the quota as well). And keep in mind
that they will have to set up their own users and security for this site collection as well (which
gets tiresome after a while).
Because users are permitted to have considerable independence in what they add to their
blogs in this scenario, we are going to enable self-service site creation for this web application.
But in addition, we will make the users responsible for regularly indicating that their site is
being used. If they don’t respond quickly enough, the site collection triggering the confirmation
notice will be deleted.
Self-service site creation is a web application-wide setting configured in Central
Administration under Application Management Site Collections. Once there, click the
Configure Self-Service Site Creation link to go to the page shown in Figure 10.46. Here you
can enable self-service site creation for a particular web application. (It is also possible to see
these settings under Application Management Manage Web Applications. Simply click
the web application and click the Self Service Site Creation button in the ribbon.) When it is
enabled, all permission levels with the Self-Service Site Creation permission set (by default,
everyone but Site Visitor members) allow users to create their own site collections. There is
also an option to require a secondary contact for the site collections created in this fashion.
Generally, this is a good idea if you’re planning on enabling site use notifications, in case the
primary administrator is unavailable to receive notifications for some reason.
Go ahead and enable self-service site creation, making sure to check the box for a secondary
contact. Click OK.
Creating a self-service site creation site collection is a little different from creating a site
collection from Central Administration. With self-service site creation enabled, users without
access to Central Administration can create site collections. In addition, during the creation
process, the users will not get to choose their path or their storage quota. The default managed path
and storage quota set at the Central Administration level will be applied for them.