Shaik Mohammad Abdullah
12/06/2025, 7:18 AMAsk Inkeep
12/06/2025, 7:18 AMAsk Inkeep
12/06/2025, 7:18 AMboxes_viewer or boxes_editor that only grants access to the boxes resource (2) . Users who need boxes access would get both their project-level role AND this boxes-specific role (1) .
ā*Option 2: Model with ReBAC Relationships*ā
Since boxes are shared across projects without direct relationships, you could model this using ReBAC's resource roles and role derivation (3) (4) . For example:
⢠Create a boxes#viewer resource role (3)
⢠Directly assign users to this resource role when they need boxes access (4)
⢠This keeps the access separate from project-level permissions
ā*Option 3: Use Tenant-Level Permissions*ā
If boxes truly belong to the entire organization, you could place them at a higher tenant level (like a "global" tenant) (1) . Users would have their project-specific roles in project tenants, plus additional roles in the global tenant for boxes access (5) (1) .
The Mesa Verde demo shows a similar pattern where certain resources (like Accounts) exist at a higher level than others (5) . They use role assignments at different levels to manage this complexity .
Which approach fits best depends on whether you need inheritance, how often users need boxes access, and whether you want to track boxes permissions separately from project permissions.Ask Inkeep
12/06/2025, 7:20 AMShaik Mohammad Abdullah
12/06/2025, 7:21 AMAsk Inkeep
12/06/2025, 7:55 AMOr Weis
12/06/2025, 8:25 AM