SharePoint governance didn’t become a topic of concern in the SharePoint community until the Microsoft product team published their initial governance documents in response to the confusion and questions that the 2007 platform created with its initial release.
Last week, I made the statement that we at Summit 7 Systems love Nintex. Now, it’s easy to say you love something. But if your actions don’t back that statement up, all you’re doing is creating hot air. So, let me explain one of the areas we’re making our daily lives more efficient, internally, with Nintex.
It seems like only yesterday that SharePoint 2010 was being rolled out with much excitement over its improvements from SharePoint 2007. Here we are just a few years later and the day we knew would arrive has finally entered that 30 day “window.”
SharePoint 2016 has been infused with some of the data protection capabilities that already exist in Exchange 2013 and Office 365. Office 365 provides these capabilities for email through the Data Loss Prevention (DLP) in Exchange, Outlook, and OWA. In SharePoint 2016, you’ll use the index to find existing sensitive content (content that is deemed sensitive in one way or another, such as social security numbers or credit card numbers) in a variety of repositories, including SharePoint sites and One Drive for Business (ODB).
Every business has processes. The quality of these most often falls into one of three categories. They can be well defined, written down, understood, and followed by employees. They can be loosely defined and create uncertainty or confusion for employees. They can be undefined and leave employees to handle however they see fit.
Trust is a key issue in any discussion of cloud services. After all, when you choose a cloud service, you're trusting them to reliably deliver the promised services and to protect your data against loss, damage, and theft. This is true whether you're talking about a consumer cloud service such as Apple's iCloud or a business service such as Office 365 or Salesforce.