I'm struggling to adapt the organizations plugin to my use case, which requires dynamic roles and permissions created at runtime by users. Since the plugin seems designed around static, compile-time roles, I'm constantly fighting against its architecture.
I've tried:
Built my own RBAC system to integrate with the plugin
Considered using metadata to bridge the gap between static and dynamic roles
For example: the authClient.organization.inviteMember() method requires a role parameter that references static roles defined at compile time. I can't figure out how to map this to my dynamic role system.
Is there a way to make the organizations plugin work with runtime-created roles?
Could metadata be used to solve the static/dynamic role mismatch?
Would I be better off using Better Auth purely for authentication and building my own organizations/teams/members system from scratch?
I'm concerned that as development progresses, some of my core requirements might become even harder to implement if I continue trying to force-fit the existing plugin architecture.