Skip to content

Commit bb5ee1b

Browse files
Merge pull request #49353 from theresa-i/secure-access-updates
Verbiage update
2 parents 147330d + 1893c75 commit bb5ee1b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

learn-pr/wwl-data-ai/secure-data-access-in-fabric/includes/2-understand-fabric-security-model.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ It's helpful to envision these building blocks in a hierarchy to understand how
1616

1717
![Screenshot of Fabric access control hierarchy.](../media/data-access-controls.png)
1818

19-
A *workspace* in Fabric enables you to distribute ownership and access policies using *workspace roles*. Within a workspace, you can create Fabric data *items* like lakehouses, data warehouses, and semantic models. *Item permissions* can be inherited from a workspace role or set individually by sharing an item. Items are shared using item permissions when workspace roles are too permissive.
19+
A *workspace* in Fabric enables you to distribute ownership and access policies using *workspace roles*. Within a workspace, you can create Fabric data *items* like lakehouses, data warehouses, and semantic models. *Item permissions* can be inherited from a workspace role or set individually by sharing an item. When workspace roles provide too much access, items can be shared using item permissions to ensure proper security.
2020

2121
Within each data item, *granular engine permissions* such as Read, ReadData, or ReadAll can be applied.
2222

0 commit comments

Comments
 (0)