Skip to content

Commit 48fe532

Browse files
Merge pull request #1559 from MicrosoftDocs/main638754123317373183sync_temp
For protected branch, push strategy should use PR and merge to target branch method to work around git push error
2 parents 3850549 + 0bdff83 commit 48fe532

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

docs/security/service-admin-row-level-security.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,10 @@ To manage security on your semantic model, open the workspace where you saved yo
3939

4040
:::image type="content" source="media/service-admin-row-level-security/dataset-more-options-menu.png" alt-text="Screenshot showing the More options menu with Security selected.":::
4141

42-
Security takes you to the Role-Level Security page where you add members to a role you created. Contributor (and higher workspace roles) will see **Security** and can assign users to a role. As a note you can only manage security on models that have row-level security roles already defined in Power BI Desktop or when editing your data model in the Power BI service.
42+
Security takes you to the Role-Level Security page where you add members to a role you created. Contributor (and higher workspace roles) will see **Security** and can assign users to a role.
43+
44+
> [!NOTE]
45+
> You can only manage security on models that have row-level security roles already defined in Power BI Desktop or when editing your data model in the Power BI service. If your model doesn't have roles already defined, you can't manage security in the Power BI service.
4346
4447
## Working with members
4548

0 commit comments

Comments
 (0)