-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Entity based (more granular) permissions #617
Comments
Hi, can you illustrate the idea a bit more fully. It is not totally clear what you mean from that description. Ideally provide some usage examples with code (can be pseudo-code). |
Sure. Let me clarify with an example. Suppose an admin is not allowed to delete any payment method. Some form of custom permission that can be assigned to him/her for that restriction. And similar for any other mutations. |
OK, so are you asking for more granular permissions, so rather than |
Yes exact
…On Thu, 18 Feb 2021, 19:05 Michael Bromley, ***@***.***> wrote:
OK, so are you asking for more granular permissions, so rather than
UpdateSettings, we have UpdatePaymentMethod, UpdateTaxRate etc?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#617 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHC2HSSZJWZX57CARPDN443S7UH3LANCNFSM4VU32YNA>
.
|
any update on this , this will be great help o restrict some setting access . currently its either having all or nothing |
Having entity-based custom permissions seems to be needed in some cases. So, allowing to restrict permission to admins on pre-built mutations can be a great feature if that is possible.
The text was updated successfully, but these errors were encountered: