Roles, Memberships, Permissions. Built for Scale.
Rolix gives Laravel applications a consistent access-control core. Stop scattering ad-hoc permission checks across modules and start managing hierarchical roles, scoped memberships, and file-based permissions with Gate, middleware, Blade, and DomainEvent support.
Why Rolix?
Complete Freedom in Access Design
Model system-wide roles and tenant-scoped memberships in the same package. Use collections, owner shortcuts, super roles, and allow/deny wildcards to match real product rules.
Unmatched Speed for Authorization Checks
Permission evaluation is memoized on the personable model for the current request and can be stored in Laravel Cache with versioned invalidation when memberships or roles change.
Unlimited Flexibility
Register role types, rule evaluators, and permission files from your app or other packages. Hook into DomainEvents for automation and keep an activity log for audits.
Core Concepts
| Concept | Meaning |
|---|---|
| Role | Named allow/deny set, optional hierarchy and rules |
| Membership | Personable ↔ role link in system or memberable scope |
| Permission | String key from permission files (hero.view, hero.*) |
| Role type | Registry key (system, tenant, …) with options |
| Rule evaluator | Runtime driver that can veto a role |
What Awaits You?
By adopting Rolix, you will:
- Centralize RBAC — roles, memberships, and permissions in one package
- Support multi-tenancy — memberable contexts, collections, and owners
- Integrate with Laravel — Gate, middleware, Blade, and helpers
- Stay extensible — registries, DomainEvents, and permission path events
- Stay auditable — activity logs for role and membership lifecycle