Creating collections Open **Workflows** from your workspace sidebar Click **New Collection** and provide a clear name Explain what types of workflows belong in this collection Add an icon, emoji, or color to make the collection easily identifiable Optionally nest this collection under a parent for hierarchical organization *** Organization strategies Choose an approach that matches your team structure and workflow needs. Organize collections by team or department. Each team manages its own automations. **Example structure:** * IT Operations (Server Monitoring, User Onboarding, Security Alerts) * HR Processes (Employee Onboarding, Time Off Requests, Performance Reviews) * Customer Support (Ticket Routing, Escalations, CSAT Surveys) Organize collections by business function. Works well when teams share automation across processes. **Example structure:** * Incident Management (Alert Routing, On-Call Escalation, Post-Incident Workflows) * Access Management (User Provisioning, Access Requests, Offboarding) * Ticket Management (Auto-Assignment, Status Updates, Notifications) Organize collections by external system. Works well when workflows are focused on specific integrations. **Example structure:** * Jira Workflows (Issue Creation, Status Sync, Escalations) * Okta Workflows (User Provisioning, Group Management, Access Reviews) * Slack Workflows (Notifications, Approvals, Alerts) *** Collection hierarchy Collections support nested structures that mirror your organization or business processes. Create hierarchical structures by nesting collections: parent collections contain related child collections, and you can reorganize by changing parent-child relationships at any time. **Example:** An “Engineering” parent collection contains “Backend”, “Frontend”, and “DevOps” child collections. *** Managing collections Editing collections Update collection name, description, appearance, or parent relationship at any time. Changes do not affect workflows within the collection. Moving workflows and collections Move workflows and collections between locations as processes change. **Drag and drop:** 1. Click and hold on a workflow or collection 2. Drag to the target collection or breadcrumb 3. Release to move To move multiple items, select them using checkboxes, then drag any selected item. All selected items move together. You can also drag items to the “Move to new folder” button to create and move in one action. **Bulk move:** 1. Select workflows or collections using checkboxes 2. Click the **Move** action in the toolbar 3. Choose the target collection and confirm **Move restrictions:** * Workflows retain their history and configuration when moved * Collections cannot be moved into their own subcollections (prevents circular references) * Moving a collection also moves all workflows and subcollections within it Deleting collections Deleting a collection also deletes all workflows within it. Collection deletion is permanent and affects all contained workflows. Export or move workflows before deleting if you want to preserve them. Permissions Control who can create, edit, or delete workflows within collections based on workspace roles and permissions. *** Tips * **Use descriptive names.** Choose names that clearly indicate the collection’s purpose. Avoid vague names like “Misc” or “Other” that become catch-alls. * **Keep hierarchy shallow.** Limit nesting to 2-3 levels deep. Deeper hierarchies become difficult to navigate. * **Indicate ownership.** Use the description field to note which team or person owns each collection. * **Review regularly.** Periodically remove unused collections, consolidate similar ones, and update descriptions as processes evolve. * **Start simple.** Begin with a basic structure and add complexity only as needed. Splitting collections is easier than merging them. Learn more about [building workflows](/documentation/automate/workflows/workflow-builder) and [publishing workflows](/documentation/automate/workflows/publish)