Pipe folders
You can control access to individual pipe folders and subfolders within a role's permissions. This allows you to restrict visibility and actions on sensitive pipes to specific users, without affecting access to other areas of the Pipes module.
Folder-level permissions apply to the View, Edit, and Delete actions available on folders and their contents. Permissions flow top-down: when you set permissions on a parent folder, all subfolders automatically inherit those settings.
Folder permissions follow a top-down inheritance model. The following rules describe default behavior and how changes propagate through a folder hierarchy:
Permissions set on a parent folder: All subfolders at every depth automatically inherit the same View, Edit, and Delete permissions.
New subfolder created under an existing folder: The new subfolder immediately inherits the parent folder's permissions.
Parent folder permissions are changed: All subfolders under that parent inherit the updated permissions. This replaces any previously configured permissions at the subfolder level.
Multi-level hierarchy, such as Folder A → Subfolder B → Sub-subfolder C: Sub-subfolder C inherits from Subfolder B. If Subfolder B's permissions change, Sub-subfolder C reflects those updated permissions.
New root-level folder created (no parent): The new folder receives View, Edit, and Delete permissions by default, as there is no parent to inherit from.
Subfolder permissions are manually restricted: Edit is removed, View is available. Users with that role can view pipes in the subfolder, but cannot edit or delete them. The parent folder's permissions remain unchanged.
All permissions removed from a subfolder: Users with that role cannot view, edit, or delete pipes within that subfolder.
If any parent folder lacks the View permission: The child subfolder and all of its contents are not visible or accessible to the user, regardless of permissions configured on the subfolder itself. This applies at every level of depth.
A folder is moved to a different parent folder: The moved folder and all of its subfolders automatically inherit the permissions of the destination parent folder. Previously configured permissions on the moved folder are not retained.
Note
When you delete a folder, all subfolders and pipes within it are also deleted. To delete a folder, your role must have Delete permission on the folder and all its subfolders. If the delete permission is absent on any subfolder, the delete action fails.
Folder permissions and pipe migrations
The following rules apply when migrating pipes or folders between organizations:
Subfolder migrated from the source organization: Subfolder-level permission settings are not carried over. The subfolder inherits the permissions of the folder in which it is placed within the target organization.
Migration creates a new folder in the target organization: The new folder inherits permissions from its parent folder in the target (standard inheritance behavior). If the folder is created at the root level, it receives View, Edit, and Delete permissions by default.
Migration into an existing target folder: The target folder's permissions are not modified or overwritten by the migration.
Non-admin user attempts to access the migration page: Access is blocked. The user sees an unauthorized error. Migration actions can only be performed by Admin users.