SharePoint
Also known as: SharePoint Online, SharePoint, team sites, document libraries
SharePoint is the Microsoft 365 service for shared file storage, team sites, and intranets.
It's where a business keeps its shared documents, organized by team or project, with permissions, version history, and co-authoring. Microsoft Teams stores its files in SharePoint behind the scenes, making it the backbone of shared content in Microsoft 365.
SharePoint, explained at three levels
At home
SharePoint is like a company filing room with labelled cabinets for each team. Each cabinet, called a site, has its own lock, so only the right people can open it. Unlike a filing room, it lives online: staff reach it from anywhere, several people can edit the same document at once, and the system keeps earlier versions of each file in case someone needs to go back.
At work
SharePoint is the Microsoft 365 service where a business keeps its shared files and builds internal websites, such as an intranet with news and policies. It replaces the old shared network drive with cloud storage that has permissions, version history, and remote access. It also sits quietly behind Microsoft Teams: every file shared in a Teams channel is actually stored in SharePoint.
At home
SharePoint is organized in layers. A site is the top level, usually one per team or project. Inside a site are document libraries, which hold files and folders, and lists, which hold rows of information like a simple spreadsheet. Permissions are set on the site and flow down to everything inside unless someone breaks that inheritance. There are two main site types: team sites for working together and communication sites for publishing news to many readers.
At work
For a workplace, SharePoint works best when the structure mirrors how the business is organized: a site per department or project, with access granted to Microsoft 365 groups rather than to individuals. Libraries can carry metadata, such as client name or document type, which makes search and filtering far better than folders alone. Every team in Microsoft Teams creates its own SharePoint site automatically, so planning one means planning the other.
At home
SharePoint's power comes from permission inheritance. Access set at the site flows to every library, folder, and file below it. The trouble starts when people share individual files with links, which quietly breaks inheritance and creates hundreds of one-off permissions nobody can audit. While SharePoint can be kept tidy, in my opinion most messes come from sharing habits, not the software, and a clear site structure set up early prevents nearly all of them.
At work
SharePoint governance covers who may create sites, naming rules, external sharing limits per site, sensitivity labels that encrypt and restrict files, and retention labels for records. Group-based permissions scale; item-level grants do not. Tools such as SharePoint Advanced Management report oversharing, which matters more now that Microsoft 365 Copilot can surface any file a user can technically reach. Native versioning and the two-stage recycle bin help, but third-party backup is still standard.
Real-world examples
At home
Lena's team kept files scattered across personal drives and email attachments, so nobody could find the latest version. Her MSP set up SharePoint sites per project, and now the whole team works from one organized, permissioned source of truth accessible anywhere.
At work
Carlos's firm moved off an aging on-site file server to SharePoint. Each department got its own site with appropriate access, remote staff could reach files securely, and version history ended the confusion of duplicate documents, all integrated with the Teams they already used.
Common confusions
- SharePoint is just online file storage — It's a collaboration and content platform, with shared libraries, intranet sites, permissions, metadata, and workflows, and it is the storage engine behind Teams files. It does far more than hold documents.
- SharePoint is too complicated for a small business — With a sensible structure set up by an MSP, small businesses use SharePoint simply as an organized, permissioned replacement for a shared drive, gaining remote access and versioning without complexity.
- Files in Teams are separate from SharePoint — Teams stores its shared files in SharePoint automatically. They're the same content viewed through different apps, which is why understanding SharePoint helps you manage Teams files.
For analysts
SharePoint done well is a modern, secure replacement for the shared network drive; done carelessly it becomes a permissions mess. Invest a little up front in a clear site structure and group-based permissions. It pays off in findability, security, and fewer 'who can access this?' headaches.
History & origin
Microsoft launched SharePoint in 2001 as an on-premises platform for document management and intranets. It grew complex and powerful over successive versions, then moved to the cloud as SharePoint Online within Office 365. As the storage layer beneath Teams and OneDrive, it became central to Microsoft 365 collaboration, though its flexibility means thoughtful structure and governance are needed to avoid disorganization.