updateProduct
One mutation, many acts: the permission depends on WHICH patch keys change, so there is no
single pair for a @permission directive to carry. The resolver requires a pair per
changing key group, and asks for nothing when the value sent is the one already stored:
AccountProfile.update— name, display_name, address_1, address_2, city, state, zip, country, business_phone, website_urlLoginSecurityPolicy.update— minimum_password_length, password_require_special_chars, mfa_enabled_at, okta_sso_requiredApprovals.manage— approvals_enabled
Every other patch key is governed by tenancy alone, because the screen that sends it offers its control to everyone. See App\Services\Permissions\ProductPatchAuthorizer.
updateProduct(
input: UpdateProductInput!
): Product


