Best way to implement a separate RBAC on part of the app

[inti]

Hello Redwood community,

What is the best way to implement separate RBAC on a part of app. I use the Redwood default one for administration of whole app (creating Users, Groups etc.).

e.g. GroupLeader can administrate his group and kick out members but is not app admin. A user can be a GroupLeader in one group and GroupMember in another Group.

Thank you for the answers

[Standup75]

Depending on what you need, I think those resource can be valuable:

Role-based Access Control (RBAC) | RedwoodJS Docs

Example of an auth directive

Lets say you have a prisma schema like this: model User { id String @id @unique username String } model Post { author User @relation(fields: [authorID], references: [id]) authorID String content String privateAuthorNotes String } You’ve done the usual SDL + services generation etc, and you have users which can write/edit/delete posts. However you have two problems with respect to access control: The privateAuthorNotes is available in the API to everyone You need to ma…