Repository navigation
Conversation
sabinem
force-pushed
the
feat/casbin-domain-hieararchy
branch
from
September 14, 2026 09:44
b04a993 to
18d8afe
Compare
Collaborator
|
Close, but reopen later: see #76. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This makes casbin automatically check hierarchical permissions, so when asking for permission on a child, it also checks permission on a parent.
so if you ask if you can do X on child t1, and you have permission for X on parent h1, it is allowed. But not the other way around, permission on a child does not give permission on the parent.
And it's still resource scoped, so permission on parent for "teams" does not give permission on a child for "project".