Updated UVCS experience overview#

Unity DevOps introduced a new experience for Unity Version Control (UVCS) to simplify repository management, enhance collaboration, and integrate permissions with Unity organizations and Unity Cloud projects.

Eligibility#

The new experience is available for all organizations that are subscribed to DevOps or are enrolled in the free trial. If you meet these criteria and are not yet on the new experience, the new experience will be enabled for your organization in the upcoming weeks.

If you have any existing repositories, DevOps creates a new Unity Cloud project, named Cloud Repositories by default, that contains those existing repositories.

What's new in the UVCS updated experience#

Repositories organized by Unity Cloud projects#

All UVCS repositories are now stored and organized within Unity Cloud projects. The integration of repositories with Unity Cloud organizations and projects removes the need to manage a separate UVCS-specific organization with its own access model.

You can group repositories under a single Unity Cloud project or distribute repositories across multiple projects, depending on your workflow.

Access repositories#

To access repositories, select the relevant Unity organization and Unity Cloud project that stores the repositories.

Permission management#

Control repository permissions at the Unity organization and Unity Cloud project levels.

• Read-only access is granted to users by default:
  • Organization members have read-only access to all repositories across all projects.
  • Project members have read-only access to only the repositories within the projects they belong to.
• Write access is granted to users with an assigned DevOps seat, for all repositories within the projects they have access to.

For more information, refer to the documentation on how to assign DevOps seats and manage members.

Storage usage tracking#

Storage usage can now be monitored and filtered by project via the Cost and usage page. For more information, refer to Cost and usage reporting.

Monitor project level storage usage#

To view project level storage usage in the Unity Cloud Dashboard, select Administration > Cost and usage, and use the Filters menu to filter by project.

Monitor repository level storage usage#

To view repository level storage usage in the Unity Cloud Dashboard, select the Unity project and navigate to either of the following:

• DevOps > Overview, and scroll down to the Storage used per repository card.
• DevOps > Version Control > Repositories.

UVCS clients#

After the update, all UVCS clients, including the desktop application, Unity Editor plugin, and command-line interface, remain fully operational and don't require any additional configuration.

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 creates a special project, named Cloud Repositories as default.

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 at the time of 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:
  • Keep the Cloud Repositories project as it is, and allow selective, manual management of user access. Refer to Grant or revoke access to the Cloud Repositories project.
• Adopt the new permissions system:
  • Convert the Cloud Repositories project to the new standard Unity organization and project permission model. This aligns repository access with Unity organization and project permissions, which grants all organization or project members read-only access while maintaining DevOps seat holder write access. Refer to Convert the Cloud Repositories project to the new permission 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 Cloud 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#

• General Documentation
• Security Documentation