How to Set Folder Permissions
Control which roles can access a folder in the Library. Admin-only. Configure role-based access for each folder you create.
Updated
by Richard Chung
Availability: 🖥️ Web | Roles: Admin
Folder permissions control which roles in your organization can access a folder and everything inside it. Use them when you want to restrict certain workflows to specific teams or roles.
How folder permissions work
A few important things to know before you start:
- Permissions are folder-level, not workflow-level. You can't permission an individual workflow on its own — only the folder it lives in
- Permissions cascade. A permission you set on a parent folder applies to every workflow and subfolder underneath it
- Default folders cannot be permissioned. My Favorites and Team Folders are open to everyone and can't be restricted
Set permissions on a folder
- Go to the Team Library
- Hover over the folder in the Library you want permission
- Click the three-dot menu (⋮) and select User Permission
- The Permissions Manager will open up and for each role select either Allow or Deny:
- Allow — users in this role can access the folder and everything inside it
- Deny — users in this role cannot access the folder
- The new permissions take effect immediately for all users on all devices
Tips
- Start with the broadest folders and work your way down. Setting permissions on a top-level folder is usually enough — the cascade handles everything inside it.
- If you have a workflow that should be visible to a different audience than the rest of its folder, move it into a separate folder with its own permissions rather than trying to permission it directly.
[TBD — clarify behavior when both Allow and Deny are selected for the same role]
For more on how roles work in StringBean, see Roles & Permissions.
How did we do?
Switching Between Libraries
Rename or Delete a Folder