How to Set Workflow Folder Permissions in Sparkforge

By Sparkforge Support Team ·Last reviewed May 3, 2026

Hover over a workflow folder, open Actions > Manage Permissions, and pick the user role allowed to see and edit workflows in that folder. Available on the Pro plan and above.

Folder Permissions restrict access to a workflow folder by user role. Users without access cannot see, create, or edit any workflows inside the folder. Available on Sparkforge Pro and above.

How to set folder permissions

  1. Open the folder menu. Hover over an existing workflow folder, or create a new one.
  2. Click Actions. Open the Actions dropdown.
  3. Manage Permissions. Click Manage Permissions from the dropdown.
  4. Pick a role. Select the user type and role allowed to access the folder. Save.

What each permission grants

Permission set toRoles with access
Agency AdminAgency Admin only
Agency UserAgency Admin, Agency User
Account AdminAgency Admin, Agency User, Account Admin
AllAll users

What folder permissions do not block

Folder permissions hide the folder from the workflow list, but every user can still:

  • See the list of workflows a contact belongs to from the Contact Details page.
  • Add or remove contacts to and from any workflow.

To restrict that level of access, use sub-account user permissions, not folder permissions.

Frequently Asked Questions

Which plan includes folder permissions?
Sparkforge Pro and above. The Standard and Classic plans manage workflow access at the user level, not the folder level.
Can a user see workflows from a restricted folder via a contact record?
Yes. Folder permissions hide the folder from the workflow list, but the Contact Details page still shows every workflow a contact belongs to regardless of folder permission.
What happens to existing workflows when I add folder permissions?
Workflows already in the folder inherit the new permission immediately. Users below the required role lose visibility on the next page load.
Can I set different permissions for view vs edit?
Folder permissions are binary — a role either has access (view, create, edit) or none. For finer-grained control, manage user roles at the sub-account level.

Was this article helpful?

Related Articles