Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

I was building a collection of requirements a Site Collection Administrator/Site Owner in SharePoint should have before being "turned loose" on their Site Collection. So Far I've come up with:

Have a very solid understanding of the purpose of SharePoint and their organization's mission in implementing the SharePoint Intranet

Reasonable understanding of basic SharePoint terminology, when asked must be able to define:Web Application,Site Collection,Sub-Site,Web Part,List,Etc…

Have a working understanding of SharePoint governance at their organization, be able to understand how it applies to them in day-to day site management.

Have a working understanding of the Organization Site Architecture. Be able to understand how they are allowed to expand on the site architecture at their department level

Have a good understanding of most SharePoint “out of the box” features, with emphasis on: Document Libraries,Lists,Blogs,Calendars,Announcements,Web Parts (implementing),Content Editor Web Part,Etc. (Be able to find a component and implement in general, advanced concepts like Forms aren’t a major concern)

Know how to create sites (including Blogs) underneath their own site, and know when it is appropriate (referencing Site Architecture) to create a site

Know how to use Permissions, understanding inheritance

Know where to go for further information, this includes: The roles IT and other departments play in SharePoint and who/when to go to for help

Other useful external sites (SharePoint Stackexchange, etc.)

Was curious what other SharePoint people have trained for in their Site Administration as well. Anything vital that you think was missed? I understand that this is probably different for every organization but there are probably some common threads. What do you think?

share|improve this question

1 Answer 1

up vote 4 down vote accepted

Site Collection Administrator and Site Owner are really two very different roles. The SCA is more of a technical role and has the ability to dramatically change the way the whole site operates, including enabling/disabling features and so forth. The Site Owner is typically content focused and is more comparable to a Power User as they can only use the features enabled on the site by the SCA and cannot make substantial changes to site structure or behavior. Of the two, the SCA would need the all of the information you list whereas a Site Owner would only need to know about a third of it.

That said, I would strongly emphasize the requirement of truly understanding permissions and inheritance. That topic alone can cause more headaches than almost everything else combined!

I would also add:

  • SharePoint Auditing as the question of Who did What and When seems to come up much more frequently than you might suspect
  • Understanding the different Recycle Bins
  • Basic list options like versioning, approvals, per-item visibility, basic workflows, incoming email, alerts, etc..
share|improve this answer
    
Good points! I should probably clarify their role would be a Site Administrator in my final checklist. Was trying to make it multi-functional though as some may later just be designated as owners. Some overlap in responsibility granted, but plenty of differentiation. –  tekiegreg Mar 21 '13 at 16:44

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.