How to Use Nested Folders to Organize Sparkforge Workflows

By Sparkforge Support Team ·Last reviewed May 3, 2026

Sparkforge workflows can live inside nested folders so you can group automations by campaign, client, or function instead of staring at one flat list.

In Automations → Workflows, folders can hold workflows and other folders. Nesting makes large libraries scannable instead of an endless flat list.

Create and manage nested folders

1. Open Workflows

Go to Automations → Workflows.

2. Create a folder

Click Create Folder, name it, save.

3. Nest a folder

Click into a folder to open it, then click Create Folder again. The new one lives inside the parent.

4. Move a workflow or folder

From the workflow list, click the three-dot menu on the row and choose Move To Folder. In the modal, navigate to the destination and click Move Here. Use New Folder if the destination does not exist yet.

5. Rename a folder

Open the folder, click the three-dot menu, choose Rename Folder, type the new name, save.

6. Delete a folder

Three-dot menu → Delete Folder → confirm. Anything inside the deleted folder moves up one level. Workflows are not lost.

Permissions on nested folders

  • Role-based access: Admins have full control; sub-users get whatever you assign.
  • Inheritance: nested folders inherit from the parent by default. Override at any folder if needed.
  • View-only vs. full control: assign per role and per folder.
  • Move and delete: moving a folder may shift its permissions to match the new parent. Deleting moves children up a level.

Best practices

  • Group by purpose: top-level folders for Marketing, Client Projects, Internal Ops; nest by campaign or phase.
  • Cap the depth at 2-3 levels. Anything deeper gets harder to navigate, not easier.
  • Restrict sensitive folders to specific team members.
  • Audit periodically. Archive or delete folders you no longer use.
  • Use search when the tree gets large. Faster than clicking through.

Frequently Asked Questions

What happens when I delete a nested folder?
Everything inside it (workflows and sub-folders) moves up one level. Nothing gets deleted along with the folder itself.
Can I share a folder with people outside my account?
No. Folder sharing is internal only. External clients cannot be granted folder-level access.
Is there a hard limit on how many folders or how many levels deep I can go?
There is no fixed cap, but going deeper than 2-3 levels usually hurts findability more than it helps.
Do nested folders inherit permissions from the parent?
Yes by default. You can override permissions on any individual folder when a sub-folder needs different access rules.

Was this article helpful?