Copying resources

What a resource package is

A resource package is a set of project items calculated by the system for copying or sharing by link. Its root resource can be:

• an automation;
• an agent;
• a delivery;
• a segment or segment consent document;
• a knowledge-base folder, file, or table;
• a standalone landing;
• a custom metric;
• a project variable;
• a lead variable definition;
• a dialog variable definition.

The exact contents depend on the root resource, related items, selected options, and user permissions. Before copying or creating a link, expand "Package items": it shows the actual contents of that package.

View access to the source resource is enough to create a package. The target project list contains only projects where you can manage every type of item in the package. For example, a package containing an agent and knowledge-base documents requires both agent management and knowledge-base management access in the target project.

Choose a transfer method

• Building a package: select several independent resources.
• Copying into a project: create a copy in a project you can access.
• Sharing by link: provide a package to a recipient and manage its access period.
• Importing from a link: review the received package and copy plan.

Before transferring, review the related resources and exceptions below.

Additional package settings

When copying an automation, the Linked automation resources setting appears. It includes linked segments and variable definitions. For a copy in the current project, you can turn it off so the copy uses resources that already exist in that project. When copying to another project, linked resources are required, so the setting stays enabled and cannot be changed.

When you create a link for an automation, linked segments and variable definitions are added automatically; you do not need to enable them separately.

When copying an agent, the interface may offer:

• including related knowledge-base sources;
• adding selected project variables and lead and dialog variable definitions.

The agent's own capability settings, such as whether voice cloning is enabled and the model selected for it, are transferred with it.

Working with operators settings are also copied: permission to hand off a dialog, group selection, and detaching the current agent during handoff. Selected groups are kept within the same project. If handoff with group selection is enabled but a selected group is unavailable, handoff is disabled in the copy until reconfigured.

When copying to another project, select operator groups again. Until then, handoff with group selection is disabled in the copy; ordinary handoff without group selection keeps its configured state. If the package contains no operator handoff settings, handoff is disabled in the copy. The copy plan and import result indicate when setup under Working with operators is required.

If Working with automations specifies selected automations, they and their dependencies are also included in the package. After import, the rule refers to automations in the destination project. All remains a rule for all automations in the destination project; it does not itself add every source-project automation to the package.

Permissions to assign other agents are not transferred. In the copy, select the allowed agents and roles again in Work with agents, and replace agent references in the instruction using the @ catalog.

An exception is access to funnel stages. Funnels are not included in the package, and a copied agent always starts in Disabled mode, even when copied within the same project. On the Tools tab, allow the required stages again and check their references in the instructions. If the original agent had this access, the import result reminds you to configure it.

If the package contains a project variable, a separate option can include its value. The value is excluded by default. Before enabling it, verify that it is not a secret or a setting that must not be transferred.

When copying into the same project, the list of extra related variables is not shown. Each option also depends on knowledge-base and variable permissions.