HOT TOPICS: Customer Experience Marketing Automation Social Business SharePoint 2013 Document Management Big Data Mobile DAM

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,  and what the 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
Admin Control: full control to all central administration and SharePoint services in virtual lab environments
Has system administrative or SQL administration rights in virtual lab environments
SharePoint Application Architect / SharePoint System Architect

Local Group Roles in the Operational Community (End-User Roles)

  • These community (site) roles will be managed by the Farm Administrator.
  • Community (site) users may belong to more than one group to add additional permissions.
  • Community (site) users may also be removed from lower level roles as higher level roles permissions may encompass the permissions of the lower level role.
Roles Responsibilities and Tasks  Training  Permissions Trustee
Site Collection Manager (IT) (Top Level Communities or Sites)
  • Manage Features and Solutions for site collection.
  • SharePoint site provisioning for site collection
Instructor led with good understanding of site administration, security, content creation, feature deployment Access defined at the SharePoint application level. No access at the system level. Farm Administrator
Site Collection Owner (Solution Manager in Development, IT in Production)
  • Site Collection Owner. Content creation. Manage content.
  • Sub-site management
Instructor led with good understanding of site administration, security, content creation Access defined at the SharePoint application level. No access at the system level. Site Collection Manager / Farm Administrator
Site Owner (Solution Manager, IT and End User)
  • Site Owner. Content creation. Manage content.
Instructor led with good understanding of site administration, security, content creation Access defined at the SharePoint application level. No access at the system level.  Site Collection Manager / Farm Administrator
Developer (IT Dev is the SharePoint Team). This group exists on all sites at time of creation but is removed prior to go-live.
  • Manage the site layout and structure.
  • Create custom workflows.
  • Create custom Web Parts, solutions and features.
  • Responsible for building the framework and features of the portal.
  • Modify SharePoint templates as needed.
  • Write ASP.Net code.
  • Participate in design tasks as needed.
  • Participate in development and testing as needed.
    Create custom forms.
Instructor led training with CBTs. MS training for Visual Studio, and SharePoint Designer “Developers” Full control of non-production systems.
Access defined at the SharePoint application level. No access at the system level.
Access does not exist in the production environment.
SharePoint Application Architect
Member Content creation (documents, lists).
Contribute to collaboration sites (blog, wiki).
Initiate workflows.
CBT with good understanding of document libraries and lists Access defined at the SharePoint application level. No access at the system level. Site Owner
Approver
  • Approve content (documents, lists).
  • Initiate workflows.
CBT with good understanding of content approval and workflows Access defined at the SharePoint application level. No access at the system level. Site Owner
Reader View content N/A N/A Site Owner

End User Community Permissions

The following is an example of “end user” community permissions based on the user roles for the community (sites) are listed below.

 

Continue reading this article:

 
 
 
Useful article?
  Email It      

Tags: , , , , , ,
 
 

Resources

 

Featured Events  View All Events | Add Your Event | feed Events RSS