Permission-heavy systems become risky when access rules are scattered across controllers, UI checks, repository filters, and background jobs. The aim is not a clever authorization framework. It is one rule path that is difficult to bypass. The examples come from Shield, Zotic, CAS, Question Banking and Amlaak.
Start with the access tuple
Every protected operation can be described with four values: the actor, the tenant, the action, and the resource. If one is unknown, the system does not yet have enough information to allow the operation.
This simple tuple prevents a common mistake: checking that a user has a permission somewhere, then loading a resource that belongs to another tenant. Permission and ownership need to be evaluated together.
The decision input
public sealed record AccessRequest ( Guid ActorId , Guid TenantId , string Action , string ResourceType , Guid ?…