Skip to main content

Project Roles

Project roles grant access to project-level data, which includes APIs that only apply to individual projects you choose. So to use some of the UGS CLI commands, you need to have the correct project roles linked to your project ID and Service Account. You can link the project roles to your Service Account and project ID under the Services Accounts section in the Unity Dashboard. For more information, see Creating a Service Account. The tables below shows the project roles required to execute commands for each module.

Environment module

Project roleDescription
Unity Environments AdminGrants full access to all environments in a project.

Access module

Project roleDescription
Unity Environments AdminGrants full access to all environments in a project.
Player Resource Policy EditorGrants write access to player-based resource policies.
Player Resource Policy ReaderGrants read access to player-based resource policies.
Project Resource Policy EditorGrants write access to project-based resource policies.
Project Resource Policy ReaderGrants read access to project-based resource policies.

Cloud Code module

Project roleDescription
Unity Environments AdminGrants full access to all environments in a project.
Cloud Code EditorGrants permissions necessary for viewing and editing cloud code resources.
Cloud Code ViewerGrants permissions necessary for viewing cloud code resources.
Cloud Code Script PublisherGrants permissions necessary for publishing cloud code scripts.

Lobby module

Project roleDescription
Unity Environments AdminGrants full access to all environments in a project.
Remote Config AdminGrants access to the Remote Config admin API.

Player module

Project roleDescription
Authentication AdminGrants access to all Admin APIs for player authentication.
Authentication EditorGrants access to all Admin APIs for player authentication.

Deploy Command

Currently Cloud Code, Remote Config and Economy services support the deploy command. To deploy for all services you need the following roles:

Project roleDescription
Unity Environments AdminGrants full access to all environments in a project.
Remote Config AdminGrants access to the Remote Config admin API.
Cloud Code Script EditorGrants permissions necessary for editing cloud code scripts.
Cloud Code Script PublisherGrants permissions necessary for publishing cloud code scripts.
Cloud Code Script ViewerGrants permissions necessary for viewing cloud code scripts.
Economy Resource EditorGrants permissions necessary for creating, editing and deleting economy resources.
Economy Resource PublisherGrants permissions necessary for publishing economy configurations.
Economy Resource ViewerGrants permissions necessary for listing economy resources.

Fetch Command

Currently Remote Config services support the fetch command. To deploy for supported services you need the following roles:

Project roleDescription
Unity Environments AdminGrants full access to all environments in a project.
Remote Config AdminGrants access to the Remote Config admin API.

Leaderboard module

Project roleDescription
Unity Environments AdminGrants full access to all environments in a project.
Leaderboards AdminGrants access to the Leaderboard admin API.

Economy module

Project roleDescription
Unity Environments AdminGrants full access to all environments in a project.
Economy Resource EditorGrants permissions necessary for creating, editing and deleting economy resources.
Economy Resource PublisherGrants permissions necessary for publishing economy configurations.
Economy Resource ViewerGrants permissions necessary for listing economy resources.