Skip to main content
Version: 2026.06

Folders

Preview

Folders is a preview feature, available behind an opt-in toggle. Turn it on under Application Settings → Experimental Features → Folders. Behavior and labels may change before general availability.

Folders let you organize the files in a system into a hierarchy, so a large system reads like a familiar directory tree instead of a flat list. You can group files by discipline, subsystem, or any structure that suits your team — for example engineering/aero/ and scratch/.

Folders describe where each file sits within a system. Organizing files into folders is an edit, and your changes are captured as a new commit when you save them.

How folders work​

A few things to know before you start:

  • Folders come from file paths. A folder exists only because files live in it. There is no separate "folder" object to manage on its own.
  • Empty folders disappear. When you move the last file out of a folder, that folder is removed automatically. You create a folder by putting a file in it.
  • Folders are per branch. The folder layout belongs to the branch you are editing. Other commits and history keep the layout they were captured with.
  • Changes are saved as a commit. Creating folders and moving files are edits you save, producing a new commit. Until you save, your changes are a draft you can cancel.

Browse folders​

  1. Open a system and select a branch or commit.
  2. The left panel file tree shows the system's files organized into their folders.
  3. Click a folder to expand or collapse it; click a file to view its preview, metadata, and actions in the right panel.

Organize files into folders​

Folder changes are made while editing the system. Enter edit mode to make changes, then save them.

Create a folder​

  1. Open the system and start editing.
  2. In the file tree, click New folder.
  3. Type a folder name and click Create.
  4. The folder appears in the tree. Move at least one file into it before you save — you cannot save while an empty folder exists.

Folder names can contain spaces and other characters; the platform stores them safely and displays the name you entered.

Move files into a folder​

  • Drag a file in the tree and drop it onto a folder to move it there.
  • To move several files at once, select multiple files and drag them onto the target folder together.
  • Drop a file onto the system root to move it out of any folder.

Nest folders​

Create a folder inside another, or drag a folder into another folder, to build a deeper hierarchy such as engineering/aero/.

Rename a folder​

Rename a folder from the tree (the New folder dialog reopens titled Rename folder). Renaming a folder updates the location of every file inside it (and any nested folders), so the whole subtree moves with the new name.

Save your changes​

Folder edits are part of the draft until you save it.

  1. Make your folder and file changes while editing.
  2. Review the resulting layout. If any folder is empty, a reminder appears — "Add a file to each folder or remove it — empty folders can't be saved" — and saving stays disabled until you resolve it.
  3. Save to capture a new commit with the new folder structure.
  4. To abandon your changes instead, cancel the draft — the system returns to its last saved state.

Saving creates a new commit, so the previous layout remains available in the system's history.

Required role: Editor or above on the system.

What folders do not change​

  • File names. Moving a file into a folder does not rename the file. Renaming a file's display name is a separate action (see Files and Content).
  • Access control. Folders are an organizational convenience; they do not grant or restrict access on their own. Sharing and permissions are managed at the system and resource level (see Sharing and Access Control).
  • History. Earlier commits keep the folder layout they were captured with; reorganizing files does not rewrite past commits.
  • Systems — systems, branches, and the file tree that folders organize.
  • Files and Content — manage individual files and their versions.