What is SharePoint Governance

SharePoint governance is the set of policies, roles, responsibilities, and processes that guides, directs, and controls how an organization's business divisions and IT teams cooperate to achieve business goals in relation to SharePoint sites and technologies.

•          People - roles and responsibilities (end users, developers, operations, security, etc.)

• Gain needed improvements through delegation and empowerment.

•          Process - how to accomplish common tasks such as creating a new site or requesting new business requirements.

•          Technology - automate enforcement by leveraging templates. Have proper policy, security settings, rights management etc.

•          Policy - documented collection of principles - for example, what users, site owners, administrators and developers should / should not do.

• Part of policy includes the information, security and customization as necessary elements so it’s clear what the proper policies are to entail.

View Video:

SharePoint Governance Core Review

SharePoint Governance Core Review

The following is a framework of what a core SharePoint review should encompass:

Commit to a 2 week time frame where all documents created to date are reviewed

Utilize whiteboard sessions, presentations and discussions to create new processes and models for governances

Create analysis and document rules for

Architecture

Roles and responsibilities

Operational plans

Development practices

Change control

Training plans

Escalation processes

Other items as applicable to your business/organization

Review for best practices and recommendations

View Video:

SharePoint Governance Review Items

The following are some key items to review with individuals in regard to governance in regard to their SharePoint sites:

Focus on what is most in need with the SharePoint Intranet, Internet or Extranet

Review the governance strategy and plan components

Review key roles, responsibilities and processes

Review an analysis of organizational support policies and procedures for SharePoint that align with administration goals

Review and analysis of operational procedures for SharePoint

Develop a SharePoint governance first draft outline and Plan (working documents)

Document process for knowledge transfer

View Video:

SharePoint is Collaborative

SharePoint is in many aspects about participation, sharing and collaboration. Overall one wants helpful, ready to use information that can be put to work quickly and easily. Thus, because of this three categories are prevalent:

1)      SharePoint is for organizations – with just a simple browser, it can be used by individuals throughout the organization. SharePoint is purpose driven encompassing an audience that includes executives, managers, decision makers, staff, etc.

2)      SharePoint is for communities – users can foster relationships based on profiles, actual communities, groups, wiki, blogs, etc.

3)      SharePoint is for public engagement – every interest in being engaged and telling a story with content on a site is key.

 

View Video:

Authentication in SharePoint 2013

This question comes up a lot from companies moving from SharePoint 2010 to SharePoint 2013 – just how does authentication work in SharePoint 2013?

-In the 2013 version – user authentication remains the same with standard sites.

-When calling a web app – the authentication happens internally.

-Internal authentication happens when calling the web app.

-External authentication – is utilized from the remote web site/application.

-To establish an app identity claims based authentication must occur.

-Incoming calls must use CSOM/REST end – points.

-Essentially the authentication is the same except that calls to the web application are authenticated with both user identity and app identity.

View Video:

Site Pages vs. Application Pages in SharePoint

The following are some key differences between site pages and application pages:

-Site pages are located in the virtual file system of a site

-Site pages enhance customizations via web part and SharePoint designer

-Site pages are rendered via a template

-Site page is ghosted to that template

-Site page when customized is un-ghosted

-Site page customization can impact performance via memory usage

-Application pages are deployed once per farm

-Application pages are accessed via _layouts virtual directory

-Application pages are compiled via ASP.NET

-Application pages don’t support user customization

-Application pages are added via farm solutions

-Application pages are compiled into a single .dll and loaded for each web application

View Video:

Excel Services & Rest Overview

The Excel services is essentially a SOAP web service which can be accessed via: http://sharepointsite/_vti_bin/Excelservices.asmx

Excel forms have fields that are bound to cells in a workbook. The form can then be filled out and populates the spreadsheet.

Common events utilized are:

              Sheet.DataEntered()

              Workbook.DataEntered()

 Workbook.BeforeTyping()

Common method utilized is:

             Workbook.Reload(call back)

REST allows for information to be accessed via OData as long as regions named as tables are in the spreadsheet

REST can be used with published spreadsheets (.xlsx)

Formatted URL example:

http://sharepointsite/_vti_bin/ExcelRest.aspx/NameofExcelFile.xslx/Odata/TableName

View Video: