Email attachments, pen drives and five versions of the same spreadsheet - or one SFTP server where every person has their own folder and everything lands in one known place. This is the office pattern that makes the quick install genuinely useful.
The server from the video becomes an office tool when its accounts mirror the office itself: one Windows user per staff member, each jailed to their own folder under one root like C:\SFTPData, plus one shared folder for team files. Setup is an afternoon of small repetitions, and the routine that follows - who puts what where, and what happens when someone leaves - is what keeps it tidy a year later.
C:\SFTPData on a drive with room to growMatch Group sftpusers block with ChrootDirectory C:\SFTP\%u, so each login is jailed to its own folderupload subfolder inside their jail - the jail root itself stays non-writable, as the chroot rules requirePersonal folders cover most exchanges, but two shared spaces complete the pattern. Shared is readable and writable by the whole SFTP group - price lists, templates, the current brochure. Drop is write-only for guests and clients: they can upload a file but cannot list or download what others sent, which is the polite way to receive files from outside. Set both through NTFS permissions on the subfolders, and say clearly in your office note which folder is for what - the technology is easy; agreed habits are the system.
Ten minutes a week is enough: glance at disk space on the data drive, clear the shared folder of files older than your agreed limit, and check the OpenSSH log for successful logins you do not recognise. Monthly, review the account register against the current staff list. The server does not need babysitting - it needs a rhythm, so problems are noticed while they are small.
This is the step offices forget, and it is the one that matters most. When a staff member leaves, disable their account the same day - in PowerShell, Disable-LocalUser -Name "username" - and change nothing else until you have taken any files their replacement needs. A departed employee's working SFTP password is a standing invitation. The register you kept makes this a two-minute job instead of an archaeological dig.
See the complete SFTP server setup on screen, step by step, in the Technical Anshu video.
Watch Full VideoPer team is usually better. People join and leave; the accounts folder keeps its purpose. Give each person their own login for accountability, but jail the logins of one team into the team folder structure.
For a small office - dozens of users moving documents - a normal Windows PC running OpenSSH is comfortably enough. SFTP serving is light work; disk space and your network will become limits long before the software does.
Only if the server is reachable from outside - through your office VPN ideally. Keep the drop account non-admin, jailed and write-only, and review what lands in it regularly.