RunCloud Workspaces are at the heart of all Business and Enterprise accounts and provide an easy way to invite teams to collaborate on resources, keep servers with different clients separate, and increase security and access control.

In this guide, you’ll learn how to move resources such as servers, deployments, and other integrations between workspaces, including from your personal workspace to another designated workspace where your team can work together collaboratively.

Begin by navigating to your account settings within the RunCloud dashboard. You can find this through your profile icon or name in the top right corner. Then, locate and click on the Manage Resources option in the left-hand menu. This will open the resource management panel.

Here, you will see a dropdown menu allowing you to select the destination workspace where you wish to move the selected items. Choose the correct workspace, and then click the Transfer button.

On the next screen, you will see a list of transferable resources. This list includes:

You will see a checkbox next to each of these items. Review this list carefully and check the boxes next to every resource you wish to move to the selected workspace.

After selecting the necessary resources, a summary screen will appear on the right of your screen. This summary will display an overview of all the items you have selected for transfer. Review this summary to verify your selection, and if everything is correct, click the Move Resources button.

A new modal window will prompt you to confirm the resource transfer. Once you confirm the transfer, RunCloud will automatically move all selected resources to the designated workspace.

Note: After transferring resources to a workspace, they must be moved back to your personal workspace individually, as bulk transfers to personal Workspaces are not supported.

Troubleshooting Git and Atomic Deployment Transfers

If a server is transferred separately from its associated Atomic Deployment Project, the web application will become disconnected from the project. When this happens, you will see an error message in your Git applications in the RunCloud dashboard.

To reconnect the Atomic Deployment, you must navigate to the Atomic Deployment Project, go to Web Applications, and reconnect the web app once both the server and its deployment project are in the same workspace.

Note: Individual servers cannot be transferred back to the personal space correctly if they have web applications with Atomic deployments linked to them. These deployments must be removed before initiating the server transfer back to the personal space. To do this, you must delete the web application from inside the Atomic Deployment Project. Therefore, be mindful of these limitations before proceeding with transfers.