Cloud Repositories update

On 2025-04-14, Unity DevOps introduced a new experience for all users of Unity Version Control (UVCS) to simplify repository management, enhance collaboration, and integrate permissions with Unity organizations and Unity Cloud projects.

If you had any existing repositories when this change went into affect, DevOps created a new Unity Cloud project, named Cloud Repositories by default, that contains those existing repositories.

Note: In the desktop application, your workspaces might not appear under the associated repository in the Repositories view. You can still find your workspaces in your list of workspaces.

Cloud Repositories project

Because of the updates to permissions, to avoid the risk of exposing sensitive repositories to all members of your Unity organization, DevOps created a special project, named Cloud Repositories as default. DevOps only creates a Cloud Repositories project for accounts that have existing repositories when they update to the new experience.

The Cloud Repositories project has different access controls to standard projects. These specific permissions ensure that only users that previously had access to the repositories can access them after the update.

Pre-existing repository permissions

The Cloud Repositories project contains all your pre-existing repositories, and retains any existing permissions that apply to those repositories:

  • Pre-existing repositories maintain their previous security and access controls, so only users with an assigned DevOps seat at the time of the update can access these repositories.
  • Members of the Unity organization don't get automatic access to the repositories in the Cloud Repositories project to ensure no widening of permissions.

This setup maintains secure and predictable access but gives you the option to align repository permissions with Unity’s standard organization and project model if you choose to do so later.

Manage your Cloud Repositories project

After the update, the Cloud Repositories project functions the same as any other Unity Cloud Project. You can rename this project at any time to better fit your organization's preferences.

You can continue to use the Cloud Repositories project indefinitely to store and manage your repositories. If you manage the project permissions appropriately, the Cloud Repositories project can serve as a permanent location for your repositories under the same access model used before the update to the new experience.

You have the following options to manage the Cloud Repositories project:

  • Maintain the current model:
  • Adopt the new permissions system:
  • Move repositories:
    • If you want to organize repositories differently, you can move repositories to another Unity Cloud project, and the standard Unity organization and project permission model applies.

Grant or revoke access

To grant a user in your organization access to the repositories in the Cloud Repositories project, do both of the following:

  • Add the user to the Cloud Repositories project as a project member.
  • Assign the user a DevOps seat.

To revoke a user's access to the repositories in the Cloud Repositories project, do either of the following:

  • Remove the user as a project member.
  • Revoke the user's assigned DevOps seat.

Convert to the new permission system

If you convert your Cloud Repositories project to the new permission system, the new permission model applies:

  • All members of the Unity organization and project gain read-only access to all repositories in the Cloud Repositories project.
  • Members of the Unity organization and project who also have an assigned DevOps seats gain write access.

To convert the permissions:

  1. In the Unity Dashboard, open the Cloud Repositories project.
  2. Navigate to DevOps > Version Control > Permissions.
  3. Select Convert to standard permissions, then confirm the action.
  4. Update the project’s access settings as needed.

Missing Cloud Repositories project

If you can't find a Cloud Repositories project in your Unity Cloud organization, there are the following possible reasons:

  • The project has been renamed by someone in your organization:
    • After the update, an organization admin can rename the Cloud Repositories project. Check with your organization’s admins or review the list of Unity Cloud projects in your organization to locate the renamed project.
  • Your organization didn’t have any repositories during the update:
    • If your organization didn’t have any repositories before the update, DevOps doesn't create a Cloud Repositories project. Only organizations with existing repositories at the time of the update have this project.
  • You are part of a new organization that signed up after the update:
    • If your organization signed up for Unity DevOps after the update, you already use the new experience and don't need the Cloud Repositories project. Your repositories automatically link to specific Unity Cloud projects based on your organization and project structure.

Additional Resources

Unity logo Documentation
Copyright © 2025 Unity Technologies
"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.