> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ravenna.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Collections

> Group related Ravenna workflows into collections by team, department, or business process to keep automation organized as your library grows.

Organize related workflows using collections. Group automation by team, department, or business process to keep workflows manageable as the number of workflows grows.

## Collections overview

Collections are folders that organize workflows. They support unlimited nesting, custom icons and colors, and descriptions. Each workflow belongs to zero or one collection.

***

## Organization recommendations

**By department** works best when teams own their automations independently. Each team manages workflows in their collection without affecting others. Example: IT Operations, HR Processes, Customer Support as top-level collections.

**By process** works best when workflows span teams. Group all workflows related to a business function together regardless of which team owns them. Example: Incident Management, Access Management, Ticket Management as top-level collections.

**By integration** works best when workflows are tightly coupled to specific external systems. Group all Jira-related workflows together, all Okta workflows together, etc.

**In practice,** most organizations use a hybrid: top-level collections by department or process, with subcollections for specific integrations or sub-processes within each.

***

## Hierarchy best practices

* Keep nesting to 2-3 levels. Deeper hierarchies become hard to navigate.
* Use descriptive names that indicate purpose, not vague labels like "Misc" or "Other."
* Note ownership in the collection description (which team or person is responsible).
* Review and consolidate periodically. Remove empty collections and merge overlapping ones.

***

## Duplicating workflows

Two duplication options are available from the workflow row menu:

* **Duplicate.** Creates a copy in the same workspace. All steps, configuration, and dynamic value references are preserved. The copy is created in `Draft` state.
* **Duplicate to Workspace.** Creates a copy in another workspace within the same organization. The user must be a non-Guest member of the target workspace. Workspace-scoped resource references — queues, statuses, tags, request types, categories, SLAs, task templates, and Slack channels — are cleared on the copy. Organization-scoped references — users, user groups, applications, access levels, access policies, code actions, and approval templates — are preserved. Cross-organization duplication is not allowed.

In both cases the copy is independent. Editing the original does not affect the copy.

***

## Constraints

* Deleting a collection deletes all workflows within it. Move workflows out before deleting if you want to preserve them.
* Collections cannot be moved into their own subcollections (prevents circular references).
* Moving a collection moves all contained workflows and subcollections with it.
* Workflows retain their configuration and execution history when moved between collections.