SharePoint Online Setup Guide for Small Businesses

SharePoint Online is included with most Microsoft 365 business plans and serves as the backbone for document storage, intranet pages, and team collaboration sites. Despite its central role, many small businesses leave SharePoint in its default state — a blank hub site and a collection of auto-created team sites from Teams — without a coherent structure. This guide covers how to set SharePoint up intentionally from the start.

Planning Your Site Architecture

Before creating any sites, plan your information architecture. SharePoint online supports two primary site types: Communication Sites and Team Sites. The distinction matters for how you structure your environment.

Communication Sites are designed for broadcasting information to a broad audience. Use them for company intranets, HR portals, policy libraries, and news hubs. They are read-heavy — a smaller group of authors publish content, and a larger audience reads it.

Team Sites are collaboration spaces. Each Microsoft Teams workspace automatically creates a Team Site. Use Team Sites for active document collaboration, project file storage, and departmental working spaces.

Configuring a Hub Site

A Hub Site connects related SharePoint sites so users can search across them, navigate between them, and see news from all associated sites in one place. For a small business, designating your Communication Site as a Hub Site and associating your Team Sites with it creates a coherent navigation experience.

To designate a site as a Hub Site, go to the SharePoint Admin Centre, select Sites, then Active Sites, select the site you want as the hub, and from the three-dot menu choose Hub, then Register as Hub Site. Then associate other sites by selecting each Team Site and choosing Hub, then Associate with a hub.

Setting Up Document Libraries

Document libraries are the core storage unit in SharePoint. Each site has a default Documents library. For small businesses, additional libraries within a site are often preferable to creating entirely new sites. Consider creating separate libraries for different document types — Contracts, Policies, Finance, Projects — rather than using folders within a single library.

Metadata Over Folders

One of the most important SharePoint best practices is to favour metadata columns over deep folder hierarchies. Folders make sense for organising physical files but restrict how documents can be searched, filtered, and viewed in SharePoint. Adding metadata columns — Document Type, Department, Project Name, Status — allows documents to appear in multiple filtered views without duplication.

Create custom columns via Library Settings, then Columns, and add them to the default view or create dedicated views filtered by column values. This single practice transforms document discovery in SharePoint.

Permissions Architecture

SharePoint permissions operate at three levels: Site, Library, and Item. Keeping permissions as high in the hierarchy as possible reduces administrative complexity. Avoid breaking permission inheritance on individual files unless absolutely necessary — it creates invisible permission walls that confuse users and complicate auditing.

Site Permission Groups

Each SharePoint site has three default groups: Owners (full control), Members (edit), and Visitors (read). Manage membership in these groups rather than granting permissions directly to individuals. Assign Microsoft 365 Groups or security groups to SharePoint permission levels so that membership changes automatically reflect in SharePoint access.

External Sharing

Review external sharing settings at both the tenant level and per-site level in the SharePoint Admin Centre. Options range from Anyone (no sign-in required) to Only people in your organisation. For most small businesses, New and existing guests (requiring sign-in and authentication) is an appropriate balance between functionality and security. Avoid tenant-wide Anyone sharing unless your business model specifically requires it.

Creating Pages and the Company Intranet

SharePoint Communication Sites include a page editor for building modern intranet pages without any coding. Use web parts to embed news, people cards, document libraries, Power BI reports, and upcoming events. A well-structured company intranet reduces time spent searching for policies, contacts, and announcements.

The News web part automatically surfaces news posts from the current site and any associated hub sites. Encourage department heads or team owners to post news regularly — this is what keeps the intranet active and worth visiting.

Version History and Retention

SharePoint maintains version history for all documents by default. Users can restore previous versions at any time from the file's version history panel. By default, SharePoint keeps all major versions indefinitely. For storage management, set a version limit in Library Settings — 500 major versions is a sensible ceiling for most document libraries.

Configure retention policies via Microsoft Purview to ensure documents are retained for the required period and deleted securely after their retention period ends. This is particularly important for regulated industries.

OneDrive Sync and Offline Access

Users can sync SharePoint document libraries to their local devices via the OneDrive sync client. Once synced, files appear in File Explorer or Finder under the organisation name alongside personal OneDrive files. Changes sync automatically when the device is online. Admins can control which sites and libraries users are allowed to sync via Group Policy or Intune settings.