Folder Taxonomy and Server Organization

Open the data root of any transfer server older than three years and you will find archaeology. There is a folder called new, a folder called new2, and a folder called temp_DO_NOT_USE that everyone uses. There is also a partner root whose name is the surname of an account manager who left. Permissions, automation, and humans all follow folder structure. So a confusing structure is not untidy. It is a security and operations problem wearing a cardigan.

This series designs a structure that explains itself. It covers inbox and outbox conventions everyone understands, and per-partner roots built from a template. It covers internal and project folders with owners, and archives that stay navigable years later. It also covers the document and scripts that keep the taxonomy from drifting. File naming lives in its own series, and volume layout in the storage series. Here we organize the tree.

Articles in This Series

• Why Folder Structure Is a Security and Operations Control
  Permissions follow folders, automation follows folders, people follow folders. The article shows how a messy tree causes leaks, failed jobs, and lost files. It tells the story through a synthetic server's slow descent into new2.
• Inbox and Outbox Conventions That Everyone Understands
  The article covers direction named from a fixed perspective, and processed, archive, and error subfolders. It explains what goes where, who may touch it, and the naming standard. It also covers the ambiguity that causes files to be sent back to their sender.
• Per-Partner Folder Structures and the Root Layout
  The article covers one root per partner from a template, the skeleton script that builds it, and permissions per folder. It covers home directories and jails that match the tree, and the partner who needs two flows.
• Internal, Department, and Project Folders
  The article covers internal exchange without a free-for-all and department roots with owners. It covers project folders with a start, an end, and a cleanup. It explains the difference between a transfer folder and a file share.
• Archives That Stay Navigable
  The article covers date-based hierarchies, indexes and manifests, and keeping archived structure parallel to live structure. It covers retention hooks, restore paths, and the archive nobody can find anything in.
• Documenting and Enforcing the Folder Taxonomy
  The article covers the one-page standard, the skeleton generator, and drift detection scripts that flag folders outside the pattern. It covers an exceptions process and cleaning up an existing server without breaking live flows.

Explore More Topics

This series is part of the Sysax file transfer topic library. The library covers the protocols, security practices, automation techniques, and operational skills behind reliable file transfer. The library pairs well with the practical tools we build. Sysax Multi Server is a secure FTP, FTPS, SFTP, and HTTPS server for Windows. Sysax FTP Automation schedules and scripts secure transfers so the routine ones run themselves.