![\"aoothjs\"](\"https://aooth.moost.org/logo.svg\"){kind=logo}
\n \n\n \n \n \n
\n Moost RBAC integration — DI-injectable MoostArbac, an authorize interceptor, @ArbacResource / @ArbacAction decorators, AsArbacDbController for scoped DB controllers, and auto-wired provider plumbing for .as user models.\n
\n Documentation →\n
\n\n---\n\n## Install\n\n```bash\npnpm add @aooth/arbac-moost @aooth/arbac @aooth/user\n```\n\n## Documentation\n\nFull docs, API reference, and recipes: **https://aooth.moost.org/moost/**\n\n- [Setup](https://aooth.moost.org/moost/setup)\n- [`@ArbacAuthorize`](https://aooth.moost.org/moost/arbac-authorize)\n- [DB controllers (`AsArbacDbController`)](https://aooth.moost.org/moost/db-controllers)\n- [Atscript wiring (`@arbac.*` annotations)](https://aooth.moost.org/moost/atscript)\n- [Decorators](https://aooth.moost.org/moost/decorators)\n- [API reference](https://aooth.moost.org/api/arbac-moost)\n\n## Custom action handlers — your responsibility\n\nThe `@ArbacAuthorize` interceptor gates the **entry** to a `@DbAction` handler: if the user lacks the privilege, the handler doesn't run. But what the handler does inside its body is on you — the interceptor doesn't follow secondary database calls or external side effects.\n\nIf your handler reads or writes rows from the same table the entry-gate scopes, route those calls through the active scope. `useArbac().getScopes