Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update data-access-control-model.md #1126

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update data-access-control-model.md #1126

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions docs/onelake/security/data-access-control-model.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -233,6 +233,18 @@ Files/
## How OneLake RBAC permissions are evaluated with Fabric permissions

Workspace and Item permissions let you grant "coarse-grain" access to data in OneLake for the given Item. OneLake RBAC permissions enable you to restrict the data access in OneLake only to specific folders.
The evaluation logic is as follows:
```
Request from user1 to read OneLake folder1 in a lakehouse
GRANT = FALSE
IF workspace permissions for coarse-grain workspace access
GRANT = TRUE
ELSEIF lakehouse permissions for coarse-grain item access
GRANT = TRUE
ELSEIF OneLake RBAC permissions for fine-grain folder access
GRANT = TRUE
RETURN GRANT
```

:::image type="content" source=".\media\security-flow.png" alt-text="Diagram showing the order of permissions evaluations with workspace, item, and RBAC.":::

Expand Down