How To5 min read·Mar 20, 2026

How to Set Up a Shared Folder for a Small Team Without a Server

You do not need a Windows Server or NAS to give a small team access to a shared folder. Here is the simplest setup that works on standard Windows 10 and 11 machines.

Quick answer

You do not need Windows Server or a NAS to give a small team a shared folder — a standard Windows 10/11 PC can host one. Pick a machine that stays on, create the folder, set the network profile to Private, enable File and Printer Sharing, then share the folder with the right permissions. The catch is that this "host" PC must stay awake and healthy; for pure file handoffs a LAN transfer app avoids needing a host at all.

You Do Not Need Server Hardware for This

A persistent misconception in small offices is that shared folders require a server — a dedicated machine running Windows Server, or at minimum a NAS appliance. For a team of 2–8 people, that is not true. Any Windows 10 or 11 machine on the office network can host a shared folder that all team members access.

The catch is that the machine hosting the folder needs to be powered on when colleagues want to access it. If that is acceptable — and in most small office setups it is, since at least one machine runs during work hours — the built-in Windows sharing approach is entirely sufficient.

Step 1 — Choose the Host Machine

Select the machine that is most reliably on during working hours. This does not need to be a dedicated machine — a staff member's primary workstation works fine as long as it stays on.

If no reliable machine exists, consider:

  • Setting the host machine's power settings to prevent sleep: Settings → System → Power → Screen and sleep → Never (when plugged in)
  • Enabling Wake-on-LAN if the machine needs to be off during evenings but accessible in the morning before its owner arrives

Step 2 — Create the Folder Structure

On the host machine, create a root folder for shared content. Keep it on a drive other than C: if possible (less affected by OS reinstalls):

D:\Shared\
  └── Projects\
  └── Templates\
  └── Documents\
  └── Resources\

The exact structure does not matter — use what reflects how your team thinks about files.

Step 3 — Set the Network Profile to Private

Sharing only works reliably on Private networks. On the host machine:

  1. Open Settings → Network and Internet
  2. Click your active connection (WiFi or Ethernet)
  3. Under Network profile type, select Private network

Step 4 — Enable File and Printer Sharing

  1. Open Settings → Network and Internet → Advanced network settings → Advanced sharing settings
  2. Under Private networks, turn on:
    • Network discovery
    • File and printer sharing
  3. Under All Networks, consider whether to keep Password protected sharing on or off:
    • On (recommended): users need credentials to access the share
    • Off: any machine on the network can access shared folders without authentication

Step 5 — Share the Folder

  1. Right-click the root shared folder (e.g., D:\Shared) → Properties
  2. Go to the Sharing tab → click Advanced Sharing
  3. Check Share this folder
  4. Set the Share name (this is what colleagues will type to connect; keep it simple: Shared)
  5. Click Permissions:
    • To allow everyone to read and write: add Everyone, set permissions to Full Control
    • To restrict: add specific user accounts with specific permissions
  6. Click OK and Apply

Step 6 — Connect From Other Machines

On each colleague's machine:

Option A — Browse: Open File Explorer → left sidebar → Network → find the host machine → open the Shared folder

Option B — Direct address: Open File Explorer → address bar → type \\HOSTNAME\Shared → press Enter (Replace HOSTNAME with the host machine's computer name, visible in Settings → System → About)

Option C — Map as a permanent drive:

  1. Open File Explorer → right-click This PCMap network drive
  2. Choose a drive letter (e.g., Z:)
  3. Enter \\HOSTNAME\Shared
  4. Tick Reconnect at sign-in
  5. Click Finish

The shared folder will appear as Z: (or your chosen letter) every time Windows starts.

Handling Authentication

If password-protected sharing is enabled, Windows will prompt for credentials when a colleague first connects. They should enter a username and password that exists as a local account on the host machine.

For simplicity across a small team: create one shared local account on the host machine (e.g., officeuser with a shared password). All team members use these credentials. More granular access control — per-user, per-folder — requires individual accounts per person.

When to Upgrade to a NAS

The single-host Windows share approach has one meaningful limitation: it depends on one person's machine being on. When that machine goes in for repairs, gets taken home, or gets upgraded — the shared folder is unavailable.

A NAS device (Synology, QNAP) is always on, does not depend on any particular person's machine, and provides better access logging. For teams that have been using the above setup for a while and keep running into the "host machine is off" problem, a NAS is the right next step.

For day-to-day file handoffs between colleagues that do not require a permanent shared location, a LAN transfer tool removes the dependency on the host machine entirely. Oxolan handles peer-to-peer transfers within your network, with no shared folder configured on either side.

Get Oxolan for Windows

Frequently asked questions

Can I set up a shared folder without a server?

Yes. Any Windows 10 or 11 PC can host a shared folder for a small team: create the folder, set the network to Private, enable File and Printer Sharing, and share it with per-user permissions. No server or NAS is required — though the host PC needs to stay powered on for others to reach it.

What is the catch with hosting a share on a normal PC?

That PC becomes a dependency: if it sleeps, reboots for updates, or is switched off, the share disappears for everyone. It also competes for that machine's disk and network. For moving files between people (rather than a permanent shared archive), a peer-to-peer app like Oxolan avoids needing an always-on host.

Is a shared folder or a transfer app better for a small team?

A shared folder suits a permanent common location everyone reads and writes; a transfer app suits handing specific files to specific people. Many small teams use both — a shared folder for the "current projects" archive and a LAN tool for quick, large handoffs that would bog the host PC down.

Skip all of these steps

Oxolan does this part automatically — install it on both machines and drag the file across. That is the whole tutorial.

Get Oxolan free for 14 days