Issue:
- Users in an organization cannot access Unity Build Automation (UBA) functionality.
Environment:
While some users can access UBA functionality on the Unity Cloud Dashboard, others cannot, even though they are members of the organization.
Cause:
Unity Build Automation uses organization and project-level access to determine access to the service for individual users. While an individual can be a member of an organization, if they are an organization "User" rather than a "Manager" or "Owner" they will need to be assigned to the project in question.
Unity Build Automation requires a user to be added directly to the project, rather than other services which only require that the user be in the organization to access them.
Resolution:
To ensure users have access to the desired project in Unity Build Automation, navigate to the Project tab in the Unity Cloud Dashboard and select the project from the list that populates on the right-hand side.
On the project page, select the Members tab, from which we can manage all users assigned to a given project. While the user may already appear in this list, if they are currently showing "inherited from the organization" and they have user-level access, they will need to be assigned directly to the project. To do this, simply click "Add Members" and choose the team member from the list of users already in the organization.
Once you have done this, the user's status on the project members page should now show "Individual grant" rather than "Inherited from organization" as in the next screenshot. The user should now be able to access the Unity Build Automation service.
Note: Please note that when user configuration at the project - level is set to "User - Individual grant", users can view the build history, trigger builds without overrides, and download artifacts. However, if you want them to modify build target configurations or create new build targets, their user type must be set to "Manager" at the project level. |