44
Lift RBAC restrictions for community users
planned
Activity
Newest
Oldest
F
Florian Krauthan
Not sure if it is relevant but to me having RBAC is way more important then Internationalization. So putting Internationalization behind a paywall (or maybe along the lines of more then 2 languages) is way less intrusive then not being able to fully role control my application content.
Derrick Mehaffy
Quote from Aurélien Georget from our forum a few months ago:
"Thank you all for your candid comments, it’s really appreciated! The limitation on the RBAC feature in the CE is a mandatory path for us, as some of you mentioned, we have to make money and pay the core team working full-time on Strapi.
From a user perspective, I do understand how frustrating it can be. We tried to be more generous than our competitors when we released the RBAC CE feature while also trying to give as much flexibility as necessary for most of the use cases we identified. Obviously, it doesn’t work all the time and the limitations might not make sense sometimes.
I really wanted to write this comment to share with you the future of RBAC. We invested a lot of time and effort in the v4, we don’t plan to release new paid features in the coming months, so nothing is going to change for the next 6 months. However, our end goal is to make RBAC 100% free and unlimited, hopefully, next year. We don’t have an ETA yet because we need to replace it with another one that would make sense for enterprises only.
In our vision of a modern CMS, RBAC + Internationalization should be default and free features for all. The Internationalization feature is already free and unlimited. Please allow us a bit more time to find the financial equation that would make what I just wrote possible. We want the same thing and empower millions of people to manage and share content"
See the full forum thread here: https://forum.strapi.io/t/rbac-role-based-access-control-feature-discussion/433/38
Derrick Mehaffy
planned