Feature Request / Question: Official CRUD Layer for Managing CASL Rules in DB-Driven Setups #1176
ayushjaiswalpb
started this conversation in
General
Replies: 1 comment
|
https://casl.js.org/v6/en/cookbook/intro You can find some examples there ^^^. Just pick one and ask AI agent to extend and generate a module in your backoffice for the framework of choice. I don’t see a purpose in building a reusable CRUD layer for managing rules because it will be hard to adjust it for different requirements |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Background
In our application where CASL is our sole authorization
layer. Rules are stored in a database table with columns like role_id, action,
subject, conditions, fields, inverted, is_active and loaded dynamically via
createMongoAbility().
Rules support MongoDB-style condition interpolation at runtime for tenant-scoped
access control. Rules are cached per role and invalidated on update.
The Problem
The backend plumbing is fully in place — DB-driven rule loading, cache
invalidation, and an API to update rules. What's missing is a UI that maps directly
to CASL concepts. and CRUD service layer to update the rules against the roles that casl manages.
Question
Is there any existing package or official pattern in the CASL ecosystem for:
them)?
box?
are MongoDB query objects — there's a potential injection surface here)?
Feature Request
We'd love to see an official package that provides:
subject grid per role)
This would make CASL a complete authorization platform rather than only an
evaluation engine. The evaluation side is excellent — the management side has zero
official tooling.
All reactions