Skip to content

Commit f5a52bf

Browse files
committed
Update how-to-assign-roles.md
1 parent d512075 commit f5a52bf

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

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

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,12 @@ Azure Machine Learning workspaces have a five built-in roles that are available
4040
| **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. |
4141
| **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. |
4242

43+
In addition, [Azure Machine Learning registries](how-to-manage-registries.md) have a **AzureML Registry User** role that can be assigned to a registy resource to grant data scientists user-level prermissions. For administrator-level permissions to create or delete registries, use **Contributor** or **Owner** role.
44+
45+
| Role | Access level |
46+
| --- | --- |
47+
| **AzureML Registry User** | Can get registries, and read, write and delete assets within them. Cannot create new registy resources or delete them. |
48+
4349
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** roles to permit the user to perform experiments while creating computes in a self-service manner.
4450

4551
> [!IMPORTANT]

0 commit comments

Comments
 (0)