Duplicate a Folder Tree

Quickly create folder copies while retaining essential information

How to use duplicate folder tree

Access Duplicate Folder Tree Feature

👉 To access duplicate folder tree, either right click the folder or left click the down arrow on the top right of the folder.

Select the "Duplicate Folder Tree" option in the menu

Set Duplicate Folder Options

👉 In the “Duplicate Folder Tree” action, you can enable the option to duplicate all assets within the folder tree.

• Change root folder name: You can enter a new name for the root folder when copying to easily distinguish and manage between the root folder and the copied folder.

• If a target Collection is specified for the new folder tree, duplicated assets will automatically be added to that Collection (if you’ve toggled on the duplicate assets option).

Note: There’s a maximum of 1024 assets per folder duplication as a safeguard to prevent copying overly large folders. For requests exceeding this limit, please reach out to support to increase this cap.

Information Copied during Duplication

• Folder Path: Retains the same structure as the original asset.

• Metadata: Descriptive information of the asset.

• Status: Includes sensitive, archive, license expiry dates, and other statuses.

• Tags: All tags assigned to the original asset.

• Faces & Consent: These are re-scanned at the time of duplication.

• Pending Upload Approval: If the asset is awaiting upload approval (not including version approvals), this status is retained.

Information Not Copied during Duplication

When duplicating an asset in HIVO, certain information is not copied to ensure the integrity and unique management of each asset copy. Here’s an overview of each item and why it isn’t included in the duplicated version:

• Approvals: Approval statuses do not carry over to prevent any prior approval from automatically applying to the new asset, ensuring each copy undergoes its own review.

• Comments: Comments are unique to the original asset and don’t transfer, allowing each duplicated asset to have its own distinct comment history.

• Shared Links: Links shared for the original asset are not duplicated to avoid unintentionally sharing the duplicated asset with previous audiences. New links can be generated if needed.

• Favorite Status: The favorite status doesn’t transfer to ensure that only assets intentionally marked as favorites are highlighted. Users can re-favorite the asset copy if necessary.

• Consent Information: Consent details are excluded to prevent previous consent statuses from applying automatically. This allows each asset copy to undergo a new consent evaluation if needed.

• Tasks: Tasks related to the original asset do not carry over, ensuring that each duplicate remains task-free unless new tasks are assigned specifically to it.

• SKUs: Stock Keeping Units (SKUs) are typically unique identifiers, so these are not duplicated, avoiding confusion with identical SKUs on multiple assets.

• Collections: If the original asset is part of a Collection, this association does not transfer. Duplicated assets must be manually added to Collections to maintain clarity and avoid unnecessary grouping.

• Related Assets: Links to related assets are not duplicated, allowing each copy to have a fresh start with its own set of related files if necessary.

By excluding these elements, HIVO ensures each duplicated asset is independent, enabling more controlled and intentional management of every asset copy.