Summary:
As of the March 2026 pricing update, per-seat charges and manual seat assignments for Unity Version Control have been eliminated in the Unity Cloud. Previously, users required a dedicated "DevOps Seat" to perform write or admin actions. Now, the only constraint for repository access is the user's role.
You no longer need to explicitly purchase or assign a DevOps seat before onboarding a new user or granting write access.
Procedure:
In cases where you want to grant access to a specific repository to other users, you can follow the steps below:
- Invite the team member to your Unity Organization, Keep in mind that if you add a user to the broader Unity organization level, they can access all projects and repositories within that organization
- To restrict the user's access strictly to a specific repository, add them as a member of the specific Unity Cloud Project where the repository is hosted. Users added at the project level can only access the repositories within that specific project.
- By default, a user has write access to all the repositories they have access to, determined by their project role. If you need to define more granular permissions (such as restricting a user to read-only access or making them an admin), you can manage those directly via the Unity Dashboard or the desktop client. To use the dashboard, navigate to DevOps > Version Control > Permissions and click the Edit icon next to the user. To use the desktop client, open the Plastic desktop application, right-click the repository, and select Permissions.
After the steps above, the user will have access to the repositories for which you enabled the respective permission.