How to Move Projects Between Workspaces

Overview

This guide explains how to move a project from one workspace to another in Assist.

This can be useful when a demo or pitch project needs to be transferred into a client’s workspace. Before moving a project, check the warnings carefully because its chats, knowledge and user access may be affected.

Before You Move a Project

When a project is moved:

The project and its outputs move to the destination workspace.
Project Knowledge moves with the project.
Workspace Knowledge from the original workspace will no longer be visible to the project’s agent.
Chats connected to the project remain in the original workspace.
Those chats are kept, but become unlinked from the project and no longer use its knowledge.
Anyone who still needs access to the project must have access to the destination workspace.

Check the project’s chats, knowledge and user access before continuing.

How to Move a Project

Step 1: Find the Project

Open Projects and locate the project you want to move.

Select the three-dot menu (⋮) on the project.

Step 3: Select Move

Select Move from the menu.

Step 4: Review the Warnings

Assist will display important information about:

Workspace Knowledge
Chats connected to the project
User access

Read these warnings before selecting a destination workspace.

Step 5: Choose the Destination Workspace

Open the Destination Workspace menu and select the workspace you want to move the project into.

You can only select a workspace you have permission to access.

Step 6: Move the Project

Check that you have selected the correct workspace, then select Move Project.

What Happens After the Move?

Project and Outputs

The project and its outputs will be available in the destination workspace.

Project Knowledge

Knowledge added directly to the project moves with it.

Workspace Knowledge

Workspace Knowledge from the original workspace does not move with the project and will no longer be visible to its agent.

If the project still needs that information, make sure suitable knowledge is available in the destination workspace.

Chats

Chats do not move with the project.

They remain in the original workspace and are kept, but they become unlinked from the project and no longer use its knowledge.

User Access

Users who still need access must also have access to the destination workspace.

Check this before moving the project to avoid removing access someone still needs.

Best Practices

Check which chats are connected to the project.
Review the Project Knowledge and Workspace Knowledge it uses.
Confirm that the correct users can access the destination workspace.
Double-check the destination before moving the project.
Let affected team members know about the move.

Troubleshooting

I can’t see the Move option

Check that you have permission to manage the project.
Confirm that you have access to another workspace.
Ask your workspace administrator for help if the option is still unavailable.

The destination workspace isn’t listed

Confirm that you have access to that workspace.
Ask the workspace owner or administrator to add you.
Refresh Assist and try again.

The project didn’t move

Check your internet connection.
Refresh Assist and confirm whether the project has moved.
Try again if it is still in the original workspace.
Contact Assist Support if the problem continues.

Quick Reference

Open the project’s three-dot menu (⋮).
Select Move.
Review the knowledge, chat and access warnings.
Select the destination workspace.
Select Move Project.

⚠️ Important: Your chats will not move

When you move a project to another workspace, its chats stay in the original workspace. They are kept, but become unlinked from the project and will no longer use its Project Knowledge.

Check your chats before moving the project and save anything important you may still need.