Wrax
Resource Scoping Best Practice
I have built a decent CRUD experience in the context of an admin user but I am unsure of what the best practice is for scoping resources to a user context.
For example, admin can interact with all records while I want a user to interact only with their own records e.g Posts vs My Posts.
I am currently thinking of creating new separate user specific resources based on the original admin resource
Is this sensible or have I got this wrong?
Guidance appreciated 🙂
5 replies