10 reasons putting team/department documents in SharePoint is better than shared drives: Part 2

Asset 1mazeThis post is a continuation of 10 reasons putting team/department documents in SharePoint is better than shared drives.

See part one for information about:

  1. Version history
  2. Approvals/Administration
  3. Check-in/Check-out
  4. Co-editing
  5. Archiving & retention

And below for information about:

  1. Sharing and security
  2. Remote access
  3. Metadata and views
  4. Workflows & alerts
  5. Sync & export

Continue reading “10 reasons putting team/department documents in SharePoint is better than shared drives: Part 2”

10 reasons putting team/department documents in SharePoint is better than shared drives: Part 1

Asset 1mazeYou know that one file, right? The one named “Agenda.docx” in the folder called “November” in the “2008” folder in another folder called “DO NOT Delete” in the “Archive” folder of the “Retired Committees” folder?

Me either. And chances are you don’t need it anymore. But managing team/department documents on traditional shared drives has challenges like this all the time, with management, retention, content ownership, etc. SharePoint, however, can greatly assist in keeping your content current, relevant and organized.

Of course making the switch from shared, common network drives to SharePoint can be intimidating. But the benefits of doing so are well worth the effort to make your team work more efficiently. This post will highlight 10 features in SharePoint you can’t necessarily get from shared network drives:

Part One:

  1. Version history
  2. Approvals/Administration
  3. Check-in/Check-out
  4. Co-editing
  5. Archiving & retention

Part Two:

  1. Sharing and security
  2. Remote access
  3. Metadata and views
  4. Workflows & alerts
  5. Sync & export

Continue reading “10 reasons putting team/department documents in SharePoint is better than shared drives: Part 1”