Pages

Apr 25, 2013

Understanding SharePoint's Communities: Power Users and Operational

We've already looked at the Knowledge community in SharePoint, now it's time to look at the Power User and the Operational Communities to see who they are, what their specific needs and best practices are for each.

The “Power User”\“Super User” Community

The “Power Users” \ “Super Users” who supports the “care and feeding” of SharePoint communities where I mentioned in the previous article “keep the lights on” and ensure security, performance, governance, compliance and business continuity should follow the following high-level as well as more granularly listed best practices:

sp_roles.png

Because IT and the “Operations” community is usually extremely busy working on “keeping the lights on” the “Power User” community can be your first line of defense as well as a friendly face to engage the business and work with IT to resolve community issues.

sp_communities.png

sp_knowledge.png

The “Operational” Community

SharePoint Operational Community and Related Roles support the following in SharePoint:

People (Permissions, Active Directory, Groups, etc.)

  • Roles & Teams
  • Sponsorship

Process and Policies (Enforcement)

  • Security
  • Content Management (Policy Enforcement from a technical level)
  • Hardware & Services
  • Procedures (From an automated or technical level)

Communication and Training (From a technical level)

  • Communication Plan
  • Training Plan
  • Support Plan

It is also key to have these permissions and responsibilities in the operations roles persistent throughout all communities (SharePoint sites \ farms). The roles and responsibilities defined below are specific to SharePoint Communities used for operations and maintenance of SharePoint 2013 and SharePoint 2010.

Note: These will vary based on your specific requirements as well as the site templates and technology versions you have implemented but is a very strong “core” list to pull from:

Role Responsibilities and Tasks Group Permissions Trustee
SharePoint Team Manager
  • Responsible for all SharePoint Product and Technology Efforts.
  • Leads SharePoint Steering Committee.
  • Leads SharePoint Team.
  • Major SharePoint Technology Decision Maker
SharePoint Team Full Control: full control given at the web application policy level for every web application in all farm locations.
Admin Control: full control to all central administration and SharePoint services in all farm locations.
May or may not have system administrative or SQL administration rights.
Application Manager/Infrastructure Architect
SharePoint Application Architect
  • SharePoint Development Team Lead
  • Third Party Configuration
  • Line of Business Integration
  • Governance Model/Best Practices Enforcement
SharePoint Team Full Control: full control given at the web application policy level for every web application in all farm locations.
Admin Control: full control to all central administration and SharePoint services in all farm locations.
Has system administrative or SQL administration rights in non-production systems.
SharePoint Team Manager
SharePoint System Architect
  • AD and Exchange Integration
  • Profile Synchronization
  • Patch Management (Validation and Testing)
  • Responsible for SharePoint farm infrastructure design, installation, guidelines and best practices.
  • Governance Model/Best Practices Enforcement
  • System Administrators day to day support
  • Search Administration
  • Farm Administrators day to day support
  • Third Party Configuration
SharePoint Team Full Control: full control given at the web application policy level for every web application in all farm locations.
Admin Control: full control to all central administration and SharePoint services in all farm locations.
Has system administrative or SQL administration rights in production systems.
SharePoint Team Manager
Active Directory Manager
  • Active Directory Management
  • DNS Management
  • Exchange Management
Infrastructure Team Will not have access to portal or site configuration settings and will not be able to make any changes to the application. SharePoint System Architect
Network Engineer
  • Firewalls
  • WAN
  • WAN Optimization
  • Remote Access Management
  • External Access Management
  • Load Balancing
Infrastructure Team Will not have access to portal or site configuration settings and will not be able to make any changes to the application. SharePoint System Architect
SharePoint Solution Manager
  • Responsible for SharePoint services, policies, procedures, and governance/best practice enforcement. 
  • Liaison between business users and SharePoint Team.
  • Day to day support for Site Collection Managers.
  • Serves as SharePoint champion for all locations.
SharePoint Team

Will not have system administrative or SQL administration rights.

Local Full Control– full control given at the site collection level

SharePoint Application Architect / SharePoint System Architect
SharePoint System Administrator
  • Responsible for SharePoint farm infrastructure change requests.
  • Responsible for day to day maintenance of SharePoint farm OS operations and uptime.
Infrastructure Team

Will not have access to portal or site configuration settings and will not be able to make any changes to the application.

IT Manager
SharePoint SQL Database Administrator
  • SQL Server database backup and recovery, SQL configuration, SQL upgrades and monitoring.
  • Responsible for databases, site collection, and site backups.
Infrastructure Team

Will not have access to portal or site configuration settings and will not be able to make any changes to the application.

SQL Administrative rights

IT Manager
SharePoint Solution Analyst
  • Tests custom code and third party tools in non-production systems
  • Defined requirements for proposed solutions to determine whether the solution is Commercial Off the Shelf (COTS), requires custom development or requires feature extension
SharePoint Team

Full Control: full control given at the web application policy level for every web application in virtual lab environments

 

Continue reading this article:

 
 
 
Understanding SharePoint's Communities: Power Users and Operational

We've already looked at the Knowledge community in SharePoint, now it's time to look at the Power User and the Operational Communities to see who they are, what their specific needs and best practices are for each.

 
 
 

 
Are you hiring?    Post your job today ($45 for 45 days)!
 
 
 

About Us

CMSWire is a popular web magazine published by Simpler Media Group. We focus on intelligent information management, digital customer experience management, and the emergence of social business tools and practices. Read more about us or learn how to advertise here.

More:
   - Monthly Editorial Calendar
   - Article Submission Guidelines
   - Advertiser Media Kit



Stay in the Loop

Latest Comments

Copyright © 2013 Simpler Media Group, Inc. All rights reserved. Privacy Policy. Terms of Use. v3.1.4.421 [X] [Y] [Z]

CMSWire and Digital Clarity Group are looking at how people are using Marketing Automation systems. Please take our short survey — it's only 8 questions!

Get the CMSWire Newsletter

  • Receive concise summaries of what's happening in your industry
  • Get access to exclusive reports, white papers and webinars

Join more than 26,000 of your peers:

We take your privacy seriously


Source : cmswire[dot]com

No comments:

Post a Comment