UPDATE: The Site Owner solution is now available for download. Click here for details.
If you’re like us you have struggled with this at one point or another: Who ‘owns’ a SharePoint site. We define the owner as the main business or technical contact for the site – the user responsible for the overall content, permissions, and management of the site. This is another area where SharePoint is lacking – sure there is an ‘Owners’ permission group – but that could have many users in it. It really does not identify the single point-of-contact we want to manage. When we set out to design our new templates one requirement was that we collect and display the site owner in the footer of every page so visitors had a way to identify and contact the site owner without a lot of difficulty or calling the helpdesk to inquire.
Our Site Owner control is deployed at the site collection level and is built-in to our site definition (you can also feature-staple it into existing site templates). Code in the master page renders the footer with the Site Owner stored in a property-bag:
When our users provision a new site, they are prompted to specify a Site Owner. The site cannot be provisioned without making a choice here:
Site Administrators can easily update this property at a later time via the Site Settings page:
Now this is all nice and good – users can identify the site owners and we reduced calls to our helpdesk and SharePoint support teams. But here is the cool bit. With a little PowerShell, we can instantly produce a report of all of the site owners (along with their site data) and marry that back to Active Directory to see if any of the users are disabled or deleted. This way we can make sure the Site Owner values are correctly populated and active users are managing these sites. Also great for sending out bulk-emails to the Site Owners when maintenance is required or changes are being deployed into their sites:
So there is our take on displaying and managing SharePoint Site Owners. Hope you found it interesting. Be sure to look for my tweets and blog updates from the SharePoint Connections Conference starting March 26th.