Consumption based ability.

[achtan]

Hi, how should I incorporate consumption-based permission into CASL? I have a multi-tenant app, and based on the customer's tier, I want to set up their abilities.

for example, I want to allow the creation of new articles, but I want to limit the number of articles to max 10.

Thanks!

[stalniy]

Hi

I don’t think this can work without domain or database support. And depends on how strict you want this to be.

In particular to counts, I know 2 ways:

1. You can create 10 articles upfront with hidden attribute and instead of creating you can update it repo level.
2. You can create ability in async way and check amount of articles before giving user permission but in this case you will need to use some lock system to ensure that this check cannot be overpassed with concurrent request