How to Clone Knowledge in Assist 2.0

Overview

The Clone Knowledge feature allows you to create an exact duplicate of an existing knowledge item and place it in a different location within your Assist 2.0 hierarchy. This is useful when you want to share knowledge across different levels of your organisation — for example, making project-specific knowledge available at the Organisation, Workspace, or another Project level.

Before You Start

• You must have an existing knowledge item with a "Training Complete" status.
• You should know where you want the cloned knowledge to live (Organisation, Workspace, Project, or Same Place).

Step-by-Step Guide

1. Open the Library

From the left-hand navigation, click Library. The Library is where all your knowledge, agents, and templates live.

2. Go to the Knowledge Tab

Within the Library, click the Knowledge tab in the left sub-navigation. You'll see all knowledge items scoped to your current workspace.

3. Click "Clone"

Find the knowledge item you want to duplicate and click the Clone button next to it.

4. Configure the Clone

A Clone Knowledge modal will appear with the following options:

Select your desired Destination from the dropdown and adjust the name if you'd like.

5. Execute the Clone

Click the purple Clone button to confirm. You'll see two notifications:

• "Cloning knowledge..." — the process has started.
• "Knowledge cloned successfully" — the clone is complete.

6. Verify the Cloned Item

Navigate to the destination where you cloned the knowledge to confirm it's there:

• For Organisation: Switch to the Organisation scope and open the Library's Knowledge tab.
• For Workspace: Make sure you're in the correct workspace, then open the Library's Knowledge tab.
• For Project: Open the relevant project and check its knowledge.

The cloned item will appear with its new name (e.g., "Assist Logo (Copy)") and a "Training Complete" status — ready to use immediately.

Key Things to Know

Choose the destination that matches who needs the knowledge. Organisation-level knowledge can be reused across workspaces, but its scope alone does not automatically include it in every project. Check Include Automatically and the project’s individual knowledge or tag selections. Cloning creates an independent copy, so later changes to the original do not update the clone.

Common Use Cases