User types, roles, and permissions
Learn about user types, roles, and permissions in the Unity Dashboard
읽는 시간 5분최근 업데이트: 2달 전
To control access to an organization and its projects, you assign user types and roles to organization members and project members:
- User types are the member's default permissions in the organization or project.
- User roles are the member's additional permissions in the organization or project.
참고
Unity ID user types and roles include inheritance. Users who are added to an organization with a non-guest user type inherit their user type at the project level. For example, a user with the Manager user type in their organization also has Manager-level access to all projects within that organization. You can use roles to assign different permissions to users.
User types and roles
Users are assigned permissions to a seat at an organizational level. These roles include Owner (billable), Manager, User, and Guest.
Project roles are assigned permissions to a seat that are specific to projects. For example, a Unity Pro user could be a Viewer for one project and a Contributor in a different project.
Overview of user types
The table below gives a high-level overview of the different user types.
User type | Summary |
|---|---|
| Guest | Guests have limited access to organizations or projects they're explicitly added to. For organization-level permissions, refer to the Guest column in Organization-level access. |
| User | Users can view organization members, organization settings, and projects, but not finance or billing. On projects they align with Project User baseline capabilities (view environments and settings, view services, and limited service-level write access where applicable). Refer to Organization-level access and Project-level access. |
| Manager | Managers can manage most of the organization and its projects, for example, members, settings, policies, projects, apps, and environments. Managers can't manage billing or payment details. Refer to Organization-level access (Organization Manager) and Project-level access (Project Manager). |
| Owner | Owners have the highest access, including finance, subscriptions, notifications, and full organization-level add-on role management, plus all manager-level project capabilities. Refer to Organization-level access (Organization Owner) and Project-level access (Project Owner). |
For information about which permissions are available to each user type, refer to the following tables.
Organization-level access
The following table lists organization-level permissions and whether each user type has them.
Permission | Organization Owner | Organization Manager | Organization User | Guest |
|---|---|---|---|---|
| View organization members | Yes | Yes | Yes | No |
| View organization settings | Yes | Yes | Yes | No |
| View projects | Yes | Yes | Yes | No |
| Add and remove members | Yes | Yes, except on the Owner | No | No |
| Edit organization members, except for owners | Yes | Yes, except on the Owner | No | No |
| Edit and delete organization user baseline properties | Yes | Yes | No | No |
| Edit organization settings | Yes | Yes | No | No |
| Manage organization-level add-on roles for members | Yes | Yes | No | No |
| Assign Finance Admin add-on role to organization members | Yes | No | No | No |
| Create projects | Yes | Yes | No | No |
| Edit projects | Yes | Yes | No | No |
| Archive and unarchive projects | Yes | Yes | No | No |
| Transfer projects | Yes | Yes | No | No |
| Delete projects | Yes | Yes | No | No |
| Link projects | Yes | Yes | No | No |
| Unlink projects | Yes | Yes | No | No |
| Manage organization policies (create, edit, and delete) | Yes | Yes | No | No |
| Set up personal notifications | Yes | Yes | Yes | Yes |
| Manage webhook integrations for notifications | Yes | Yes | No | No |
| Manage finance and billing settings | Yes | No | No | No |
| Manage subscription settings | Yes | Yes | No | No |
| Sign up for Unity Gaming Services | Yes | No | No | No |
| Access or delete Diagnostics data | Yes | Yes | No | No |
참고
This is a non-exhaustive overview of permissions to illustrate the levels of access for different types of users. The Organization Owner and Organization Manager roles in particular are very powerful and have further permissions not listed above.
Project-level access
The following table lists project-level permissions and whether each project role has them.
Permission | Project Owner | Project Manager | Project User |
|---|---|---|---|
| Access financial and billing information | Yes | No | No |
| Access and edit everything across all projects | Yes | Yes | No |
| View project environments | Yes | Yes | Yes |
| Create, view, and delete environments | Yes | Yes | No |
| Create and delete environment policies | Yes | Yes | No |
| Add and remove project icons | Yes | Yes | No |
| Manage project-level add-on roles for members | Yes | Yes | No |
| Edit project members, except for owners | Yes | Yes, except on the Owner | No |
| Edit and delete project user baseline properties | Yes | Yes | No |
| Manage apps (create, update, archive, unarchive, and transfer) | Yes | Yes | No |
| Edit app policies | Yes | Yes | No |
| View project settings | Yes | Yes | Yes |
| Edit project settings | Yes | Yes | No |
| Manage project policies (create, edit, and delete) | Yes | Yes | No |
| Manage groups (edit groups, add and remove members) | Yes | Yes | No |
| Edit customer data settings | Yes | Yes | No |
| Edit and delete customer data setting confirmations | Yes | Yes | No |
| Manage service accounts (create, edit, and delete) | Yes | Yes | No |
| Create and delete API credentials for service accounts | Yes | Yes | No |
| Restrict the visibility of projects | Yes | Yes | No |
| View restricted projects | Yes | Yes | Yes (project members only) |
| Enable services | Yes | Yes | No |
| View project services | Yes | Yes | Yes |
| Access and edit project services | Yes | Yes* | Yes* |
| Service-specific write access (manage features at service level) | Yes | Yes | Yes |
| Edit and delete project resource policies | Yes | Yes | No |
| Edit and delete player resource policies | Yes | Yes | No |
| Archive and unarchive projects | Yes | No | No |
| Transfer projects | Yes | No | No |
| Manage webhook integrations for notifications | Yes | Yes | No |
| Manage finance and billing settings | Yes | No | No |
| Manage subscription settings | Yes | No | No |
| Sign up for Unity Gaming Services | Yes | No | No |
| Access or delete Diagnostics data | Yes | Yes | No |
* Additional access to services, and permissions on those services, can vary by service.
Roles
An Owner or a Manager can:
- At the organization level, assign a user type and roles to an organization member. This grants the organization member access to the data and services of all projects that require this specific role. Within a project, the member's role is labeled Inherited from the organization.
- At the project level, invite an organization member, or a guest from outside the organization, to the project and assign them a user type and roles. Project members can access only the data and services of this specific project. Guests can access only the selected project. Within the project, the member's role is labeled Individual Grant.
참고
Organization members are listed as project members of all projects within their organization. However, they still need to be assigned the correct roles to access a project's data and services.