Skip to content

Commit ef7d0c0

Browse files
committed
Update how-to-assign-roles.md
1 parent 9cbb796 commit ef7d0c0

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

articles/machine-learning/how-to-assign-roles.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,15 +30,18 @@ In this article, you learn how to manage access (authorization) to an Azure Mach
3030
3131
## Default roles
3232

33-
Azure Machine Learning workspaces have a four built-in roles that are available by default. When adding users to a workspace, they can be assigned one of the built-in roles described below.
33+
Azure Machine Learning workspaces have a five built-in roles that are available by default. When adding users to a workspace, they can be assigned one of the built-in roles described below.
3434

3535
| Role | Access level |
3636
| --- | --- |
3737
| **AzureML Data Scientist** | Can perform all actions within an Azure Machine Learning workspace, except for creating or deleting compute resources and modifying the workspace itself. |
38+
| **AzureML Compute Operator** | Can create, manage and access compute resources within workspace.|
3839
| **Reader** | Read-only actions in the workspace. Readers can list and view assets, including [datastore](how-to-access-data.md) credentials, in a workspace. Readers can't create or update these assets. |
3940
| **Contributor** | View, create, edit, or delete (where applicable) assets in a workspace. For example, contributors can create an experiment, create or attach a compute cluster, submit a run, and deploy a web service. |
4041
| **Owner** | Full access to the workspace, including the ability to view, create, edit, or delete (where applicable) assets in a workspace. Additionally, you can change role assignments. |
4142

43+
You can combine the roles to grant different levels of access. For example, you can grant a workspace user both **AzureML Data Scientist** and **Azure ML Compute Operator** role to permit the user to perform experiments while creating computes in self-service manner.
44+
4245
> [!IMPORTANT]
4346
> Role access can be scoped to multiple levels in Azure. For example, someone with owner access to a workspace may not have owner access to the resource group that contains the workspace. For more information, see [How Azure RBAC works](../role-based-access-control/overview.md#how-azure-rbac-works).
4447

0 commit comments

Comments
 (0)