Permissin Check

[woeful wyvern]

Hi @silent relic as for obtaining details on why a specific permission was granted or which exact permission matched, we dont have built-in feature that provides this level of detailed insight post-access check. Access control decisions are evaluated based on stored relational tuples and your authorization model (Schema), focusing on whether the subject (user) is related to the action without specifying the 'why' in the response of a permission check. But we could improve the reasoning, could you open an issue about this so we can add it to our roadmap.

While we don’t have a concept of assigning weight directly to permissions, maybe you could potentially model such behavior by designing your schema. For instance, you might define permissions in a way that inherently prioritizes certain roles through the use of logical operators (and, or, not) to create a hierarchy of permission checks where, for example, an Administrator role inherently grants access that a Viewer role might not, depending on how you structure your conditions.