What problem does it solve? Adding or debugging access control in OrangeHRM requires understanding three layered authorization gates, permission seeding tables, and the marker interface for public routes, which is easy to get wrong and produces confusing 403 errors. ## Core Features & Use Cases - Authorization Model Reference: Documents the three-gate subscriber flow (authentication, screen permissions, API data-group permissions), effective role computation, and OR-merge semantics. - Step-by-Step Recipes: Provides checklists for adding authenticated or public REST endpoints and Vue pages, including permission/api.yaml and permission/screens.yaml seeding via migrations. - 403 Debugging Guides: Ordered troubleshooting checklists for both REST and page authorization failures, covering missing _api attributes, permission rows, dynamic roles, and the self flag. - Use Case: When adding a new REST endpoint to an OrangeHRM plugin, follow the recipe to create the Endpoint class, register the route with _api, seed role permissions through a migration, and verify access per role. ## Quick Start Ask the agent to explain how to add a new authenticated REST endpoint with role-based permissions to an OrangeHRM plugin.