Six Lists in one client Folder can be perfectly usable for the person who built the setup, yet a new team member still has to read every name before they can see which pieces belong together. Add a layer without a real reason and every piece of routine work takes another click. The decision is not whether the sidebar could look tidier. It is whether a Subfolder reflects how the team actually works.
Prefer to watch? The full walkthrough is on YouTube:
What does a ClickUp Subfolder contain?
Think of a Subfolder as an organiser tray inside a drawer. In ClickUp, a Folder answers “whose work is this?”, a Subfolder answers “which workstream does it belong to?”, and a List answers “which workflow does the team follow?”. Tasks stay in Lists. Each level should give a different answer, rather than repeating a label that is already clear elsewhere.
A Folder can contain Lists directly alongside Subfolders. That is useful when one shared List sits next to several workstreams, but the loose List needs a clear job. A name such as Shared Requests tells the team why it sits outside the workstream groups. Without that rule, the Folder becomes two competing filing systems and new work lands in the wrong place.
As of October 2026, ClickUp supports one Subfolder layer: Folder, Subfolder, Lists. Deeper nesting is in the works, but there is no confirmed delivery date. Structure around the levels available now, not a possible future branch. For the full picture of every level, see the ClickUp hierarchy guide.
When should you use ClickUp Subfolders?
Use a two-part test before adding a Subfolder:
- Name the workstreams. Can you name at least two distinct workstreams inside one Folder?
- Check what each one needs. Does each workstream need its own Lists, settings, access or reporting?
If both answers are yes, a Subfolder may earn its place. If either answer is no, keep the Lists in the Folder.
Consider a client Folder with six Lists. Grouping them under Onboarding, Ongoing Delivery, and Growth and Renewals makes the workstreams visible. The Folder still identifies the client, each Subfolder identifies a major type of work, and each List remains the place for a specific workflow. The team can tell which Lists belong together without decoding a naming convention.
If the only difference between groups is a label such as region, client type or priority, use a Custom Field and a view instead. Those are labels, not workstreams: the work moves the same way in each group, so a Subfolder per label only adds clicks.
How to set up ClickUp Subfolders for client work
Start from the work, not from the hierarchy. For a new client or project, set up its Folder and the Lists the team needs, then add Subfolders only where the test above says they solve a real grouping problem.
- Write down the workstreams first. List the distinct kinds of work that belong in the Folder. If you cannot name at least two real workstreams, stop here and keep the Lists together.
- Create one Subfolder per workstream. Place only the Lists that serve that workstream inside it. A Subfolder should explain why those Lists belong together, not give similar names a new home.
- Keep shared Lists deliberate. If a List belongs to the whole client relationship rather than one workstream, leave it directly in the Folder and give it a clear purpose, such as Shared Requests, so the team knows where new work goes.
- Stop at one Subfolder layer. If your real structure is client, project, workstream and package, do not force all four into the Folder tree. Use clearer List names, Custom Fields, views or separate Folders for the levels the hierarchy cannot hold.
- Write down what each layer means. State what the Folder, Subfolder and List each represent for your team, and which settings are shared or set lower down. Keep names short enough to scan.
Where should statuses, Custom Fields, access and Automations live?
Put shared settings at the Folder and workstream-specific settings at the Subfolder. That way nobody maintains the same client details in several places, and a rule meant for one type of work does not fire on another.
- Statuses: Subfolders inherit their parent Folder’s statuses, regardless of when they were created. Inheritance is not the problem. Keep the shared client workflow at the Folder, and give a workstream its own statuses only when its work genuinely moves through different stages.
- Custom Fields: Put fields that describe the client at the Folder, such as Client Account, Account Manager and Client Health, so every task in every Subfolder gets them. Put fields for one workstream lower down. Renewal Date and Decision Owner belong in Growth and Renewals, so a renewal question never appears on an onboarding task.
- Access: A Subfolder inherits who can see it from its Folder, so adding one does not create a new access boundary. If a workstream needs to be private, make that a deliberate choice and check who can see the Lists inside it.
- Automations: A rule on the Folder reaches every Subfolder below it. Use the Folder for rules that apply across the client relationship. A rule that only applies to renewals belongs inside Growth and Renewals, or it will also fire on onboarding work.
- Views and reporting: A Subfolder view shows tasks from every List inside it, which makes it a natural working screen for that team. A Folder Dashboard card includes every Subfolder below it.
Match the report scope to the question you are asking. A card at the Folder shows the whole client relationship. Filter it to Ongoing Delivery and you get active delivery only. They are not the same number, and an account manager who quotes the client-wide figure as delivery workload will overstate it to the client.
What to check before moving live work into Subfolders
You can turn an existing Folder into a Subfolder by moving it under another Folder. On live client work, that is a structural change, not a tidy-up, because statuses, fields, access, Automations and Dashboard filters can all shift. Test it first:
- Make a copy of the Folder. Leave the live client structure untouched while you test.
- Move the copy under the intended parent Folder. It becomes a Subfolder, which shows you exactly what the real move will do.
- Check every setting that can shift. Compare statuses, Custom Fields, access, Automations and Dashboard filters on the copy against the original.
- Move the real Folder only when the copy behaves as intended. If something no longer matches the work, fix the structure on the copy before you touch the live one.
If you run sprints, there is one more rule. As of October 2026, a Subfolder can sit inside a Sprint Folder, and a Sprint Folder can sit inside a regular Folder, but a Sprint Folder cannot sit inside another Sprint Folder. Test your sprint structure on its own before you build around it.
When you don’t need ClickUp Subfolders
Skip the extra layer when the Lists in a Folder share the same workflow, team, access and reporting. If one team owns three Lists that move through the same statuses, a Subfolder makes people open the Folder, expand the Subfolder and then open the List: an extra click with no extra meaning.
Skip it, too, when the Workspace already works. Every new layer costs the team time to relearn. If people already find their work quickly, don’t reorganise just because the option exists.
If you do add Subfolders, review them after a month of real work. Are people finding things faster? Are the settings still predictable? If not, simplify. A good drawer doesn’t have the most dividers. It has the right ones.
If your ClickUp setup feels harder to use than the work itself, take the free Business Chaos Check. It will help you find the real bottleneck before you add more structure.