Who this is for / When to use
This article is for Kyrios users who manage many workflows and need structured organization, clearer ownership, or permission control using folders within folders.
What nested folders are
Nested folders let you create folders inside other folders within the Workflow List.
This structure makes it easier to group related workflows, separate systems or clients, and manage permissions without cluttering the main workflow view.
Nested folders support:
Unlimited folder depth
Workflow movement between folders
Permission inheritance and overrides
How to create a nested folder
A nested folder is created by adding a new folder while inside an existing folder.
Go to Automation → Workflows.
Open the folder where the new folder should live.
Click Create Folder in the top-right corner.
Enter a folder name.
Click Create.
The new folder is created inside the currently open folder.
How to move workflows into folders or sub-folders
Workflows can be moved into any folder or nested folder using the Move to Folder option.
Locate the workflow to move.
Click the three-dot menu on the workflow row.
Select Move to Folder.
Choose a destination from the folder tree.
Click Move.
How to create a new folder while moving a workflow
New folders can be created directly from the Move to Folder flow.
Open Move to Folder for a workflow.
Click Create Folder in the folder selection modal.
Enter the new folder name.
Click Create.
Select the new folder and click Move.
The workflow is moved into the newly created folder immediately.
How permissions work with nested folders
Permissions for nested folders follow strict inheritance rules to prevent accidental access changes.
Root-level permission behavior
New folders or workflows inherit permissions from their parent folder at creation time.
Creating a folder inside a restricted folder applies the same restriction
Admin permissions flow down automatically to newly created sub-folders
Nested folder permission behavior
Changing permissions on a nested folder does not affect its parent.
If a root folder changes from Admin to All, nested folders keep stricter permissions
Nested folders can have more restrictive access than their parent
Moving folders and workflows
Permission behavior depends on the destination:
Moving a folder or workflow to the root level applies root-level permissions
Moving a folder with Admin permissions retains Admin access
Moving a restricted folder does not loosen permissions automatically
What happens when a folder is deleted
Deleting a folder removes only the folder itself, not the contents.
All workflows and sub-folders move up one level to the parent folder
No workflows are deleted automatically
Permissions are re-evaluated based on the new parent location
Common issues and fixes
I can’t see a folder option
Only users with permission to manage workflows can create or move folders.
Permissions changed unexpectedly after moving a workflow
Permissions always follow the destination folder’s rules. Check the parent folder permissions after moving items.
I deleted a folder by mistake
Folder deletion does not delete workflows. All contents are moved to the parent folder automatically.