Forum Discussion

terdahl's avatar
terdahl
Copper Contributor
Jul 08, 2026

New to Sharepoint and Teams_best practice for creating client folders/site

We are a small landscape design/build company moving from Microsoft 365 Family to Microsoft 365 Business Standard.

Currently, we use a traditional folder system:

Clients > Client Name > project files

Each client folder contains estimates, proposals, Vectorworks CAD drawings, site data, photos, PDFs, spreadsheets, and other project documents.

We also have other company folders for employees, equipment, systems, vendors, templates, and SOPs.

We have four office users who need to access and collaborate on these files through SharePoint/Teams.

What is the best practice for setting this up?

Should we use one SharePoint site with document libraries, separate SharePoint sites by department/category, or organize everything through Teams channels?

I’d like to understand the best way to use SharePoint and Teams without simply recreating an old folder system incorrectly.

2 Replies

  • Moving from a file server mindset to SharePoint is definitely a shift, but it's worth planning it properly from the start.

    For a company with four office users, I would keep the structure as simple as possible rather than creating lots of SharePoint sites.

    A good approach would be:

    • Create one primary SharePoint Team Site for the business.
    • Use document libraries (or a small number of top-level folders) for major business areas, such as:
      • Clients
      • Employees (with restricted permissions)
      • Equipment
      • Vendors
      • SOPs & Templates
      • Finance (if applicable)
    • Within the Clients library, continue organizing by Client Name > Project, since this matches how your team already works and makes files easy to find.
    • Only create additional SharePoint sites if a department truly needs separate permissions, ownership, or a different lifecycle. With four users, that's probably unnecessary.

    For Teams:

    • Think of Teams as the collaboration interface, not the storage location.
    • Create a Team (for example, "Office") connected to your SharePoint site.
    • Use channels only for ongoing collaboration where conversations and meetings are important—not as a replacement for your folder hierarchy.
    • Avoid creating a channel for every client, as that quickly becomes difficult to manage unless each client has active discussions.

    A few other best practices:

    • Take advantage of SharePoint metadata (e.g., Project Status, Year, Designer) if you need better filtering later, but don't feel you need to implement it on day one.
    • Keep permissions simple and assign them at the site or library level whenever possible instead of on individual folders.
    • Use version history instead of creating files like Proposal_v2_Final_FINAL.pdf.
    • Sync the main libraries with OneDrive if your team prefers working in File Explorer, while still keeping SharePoint as the source of truth.

    Given your size and the type of files you're storing (CAD drawings, PDFs, photos, spreadsheets, proposals), a single SharePoint Team Site with a well-organized Clients library is likely the easiest to manage and will scale well as your business grows. You can always split content into additional sites later if your needs become more complex.

  • Hi terdahl, for a small company I would avoid making one Team or one site per client unless permissions are very different for each client. A clean starting point is one SharePoint site for company documents, with libraries like Clients, Templates, Vendors, Equipment, and Internal Operations. Inside the Clients library, use folders or metadata by client and project, then only create separate Teams or channels where people actually need chat, meetings, and task collaboration around that work.