Documentation

​
​

Development

User Acquisition

Monetization

Industry

Unity Version Control

DevOps

On-prem

Gluon

Editor plug-in

Open Unity Dashboard

Unity Version Control

​
​
Unity Version Control
  • Overview
  • Cloud Repositories organization update
  • Installation
  • Use UVCS with the Unity Editor
  • Unity Version Control plugins
  • Concepts
  • Tutorials
    • Migrate from Git
    • Migrate from Perforce
    • Version Control settings
    • Configure the client
    • Version Control workflow
      • Set up a workspace
      • Create a repository
      • Use a nodata replica
      • Create a branch
      • Modify files
      • View file history
      • Code reviews
      • Code reviews (GUI)
      • Merge changes
    • Version Control tools
  • On-Prem
  • Gluon
  • CLI and shortcut references
  • Release Notes
  1. Unity Version Control (previously Plastic SCM)

Set up a workspace

Create a new workspace in Unity Version Control.
Read time 2 minutes
Last updated 6 months ago
To work in Unity Version Control (UVCS), you need a repository. Inside your repository, you can create a workspace, which is a local copy of a project.
Because a workspace is a local copy, you need to set up your workspace through the desktop application or the command line.
Note
If you work on Windows and you have a large amount of files, you might want to enable dynamic workspaces so that you don't have to download every file.

Create a workspace in the GUI

You can create a workspace when you create a repository, or you can create a workspace for an existing repository.
  1. Select the repository dropdown menu.
  2. Select Open or create other workspace.
  3. Select Create a new workspace.
  4. Configure the workspace.
    1. Select a repository.
    2. Name the workspace.
    3. Select a location for the files.
  5. Select Create.

Create a workspace in the CLI

  1. To create a new workspace, use the 
    cm workspace create
     command:
    >cm workspace create quakewk quake_path --repository=quake@localhost:6060Workspace quakewk has been correctly created
  2. Go to your newly created directory:
    >cd quake_path>cm status/main@quake@localhost:6060 (cs:0 - head)
    By default, the workspace uses the 
    main
    branch.
  3. To check the latest changeset on the branch, run 
    cm status --head
    :
    >cm status --headcs:573@quake@localhost:6060
  4. Run 
    update
     to update to the latest changeset:
cm update
The command provides information about the copied files until you’re up to date with the latest changeset.

Additional resources

  • If you work on Windows, you might want to use a virtual filesystem and only download files you need, refer to the introduction to dynamic workspaces and information on how to enable dynamic workspaces.
Copyright © 2026 Unity Technologies
LegalPrivacy PolicyCookiesDocumentation Terms of UseDo Not Sell or Share My Personal InformationYour Privacy Choices (Cookie Settings)

"Unity", Unity logos, and other Unity trademarks are trademarks or registered trademarks of Unity Technologies or its affiliates in the U.S and elsewhere (more info here). Other names or brands are trademarks of their respective owners.

Some pages are machine-translated for convenience, and may contain inaccuracies. In the event of conflicting information, the English version is authoritative.

  • On this page

    • Create a workspace in the GUI

    • Create a workspace in the CLI

    • Additional resources

Report a problem with this page