Skip to content

Commit 11f8989

Browse files
authored
Update catalog-permissions.md
1 parent a05d162 commit 11f8989

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/purview/catalog-permissions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ Azure Purview uses a set of predefined roles to control who can access what with
2828
- **Data readers** - a role that provides read-only access to data assets, classifications, classification rules, collections and glossary terms.
2929
- **Data source administrator** - a role that allows a user to manage data sources and scans. If a user is granted only to **Data source admin** role on a given data source, they can run new scans using an existing scan rule. To create new scan rules, the user must be also granted as either **Data reader** or **Data curator** roles.
3030
- **Policy author (Preview)** - a role that allows a user to view, update, and delete Azure Purview policies through the policy management app within Azure Purview.
31-
- **Workflow administrator** - a role that allows a user to access the workflow authoring page in the Azure Purview studio, and publish workflows on collections where they have access permissions.
31+
- **Workflow administrator** - a role that allows a user to access the workflow authoring page in the Azure Purview studio, and publish workflows on collections where they have access permissions. Workflow administrator only has access to authoring, and so will need at least Data reader permission on a collection to be able to access the Purview Studio.
3232

3333
> [!NOTE]
3434
> At this time, Azure Purview Policy author role is not sufficient to create policies. The Azure Purview Data source admin role is also required.

0 commit comments

Comments
 (0)