Have you checked by doing a simple query for the authenticated user:

query{ user{ id role } }

to check which user it thinks you are trying to run things as?

finds the user without a problem

type User implements Node { auth0UserId: String @isUnique birthdate: DateTime! createdAt: DateTime! createdEvents: [Event!]! @relation(name: “CreatedEventOnUser”) email: String! @isUnique eventRegistrations: [EventRegistration!]! @relation(name: “EventRegistrationOnUser”) id: ID! @isUnique ledEvents: [Event!]! @relation(name: “LedEventOnUser”) name: String! phone: String! @isUnique role: Role! @defaultValue(value: USER) ticketPurchaseRegistrations: [TicketPurchaseRegistration!]! @relation(name: “TicketPurchaseRegistrationOnUser”) ticketPurchases: [TicketPurchase!]! @relation(name: “TicketPurchaseOnUser”) updatedAt: DateTime! }

this query fails in the playground as well..where i can choose which user is the one who does the request

query{ allUsers(filter{id"[YOUR_USER_ID]" role:MANAGER}){ id role } }

That will check whether your permission query should be able to find a result

What does your Role enum schema look like?

(testing a permissions query as a standard query can also give more useful error messages sometimes)

is what the role looks like

and the standard query responds with a user id and role

Do you definitely have no other permission queries that could be firing? (e.g. read on the type you are trying to create or on a relationship or type if your create mutation includes nested mutations)