Folders group workflows in the sidebar. Nest or reorder them to organize a workspace by team, customer, or purpose.
The parts of a folder
Here's an example: a folder named Customer Deployments, colored red, holding five workflows and two subfolders.
Name
Choose category names such as Internal, Customer-Facing, or Ops. Use the same naming convention across your workspace.
Color
Folder colors appear as dots beside their names and default to gray (#6B7280). Change the color from the folder menu. Use color alongside clear names so the grouping is still understandable without color.
Nesting
Nest folders when a category needs subgroups, for example Production → Customer A → Deployments. Keep the hierarchy shallow enough to scan.
Order
Folders display in a set order, top to bottom, that you control by dragging them in the sidebar. Drag a folder up or down to reorder it within its level, or drag it onto another folder to move it inside as a subfolder. Order is a convention too: put the folders a team touches daily at the top.
Locking
A locked folder is read-only: its workflows can be viewed but not edited. Locking is off by default. Lock a Production folder so members can open and run its workflows without changing them by accident. Locking a folder also locks everything inside it, so a locked parent protects its subfolders and their workflows in one move. Who can lock and unlock follows the workspace roles and permissions.
Archiving
Archiving a folder removes it from your active sidebar without deleting it. An archived folder drops out of the normal view, and you restore it when you need it again. Use archiving for cleanup: a finished customer engagement or a retired experiment leaves the sidebar but stays recoverable. There is no permanent hard-delete in the folder menu, so archiving is the safe way to get something out of the way.
Conventions
Naming conventions make the structure legible to someone who did not build it. Nothing here is enforced, so the value comes from applying one rule consistently across the workspace.
- Group by audience or function at the top level. A common split is
Internal,Customer-Facing, andOps. Someone new can find the right branch from the top-level names alone. - Name folders as categories, workflows as actions. A folder is a noun (
Billing); a workflow is a thing it does (Send overdue reminder). The folder path plus the workflow name should read as a sentence. - Use color for the top level, names for everything below. Color carries the coarse grouping; names carry the detail. Mixing both at every level turns into noise.
- Mirror the convention everywhere. The same category words you use for folders are worth reusing for tables, secrets, and integrations, so a team learns one vocabulary instead of three.
One workspace or several
Folders organize workflows within a workspace. Use a separate workspace when the work needs its own members, settings, or resource ownership.
- Group in folders when everything belongs to the same team and the same access rules, and you only want it easier to navigate.
- Split into workspaces when a set of work needs its own members, its own integrations and secrets, or its own isolation. The classic case is one workspace per customer, where the workspace itself is the deliverable the customer owns.
See Workspace fundamentals for what the boundary scopes and Roles and permissions for how members and seats work across workspaces.