{"section":"known-issues","requestedLocale":"en","requestedSlug":"vtex-settings-set-cli-returns-403-even-for-account-admins-no-license-manager-resource-grants-the-required-permission","locale":"en","slug":"vtex-settings-set-cli-returns-403-even-for-account-admins-no-license-manager-resource-grants-the-required-permission","path":"docs/en/known-issues/Apps/vtex-settings-set-cli-returns-403-even-for-account-admins-no-license-manager-resource-grants-the-required-permission.md","branch":"main","content":"## Summary\n\nRunning `vtex settings set <app> <field> <value>` fails with a 403 Forbidden (`Role User:<user> in <account>/ cannot perform action PUT on resource vrn:apps:...:/apps/<app>/settings`) even when the user holds the account's highest available role in License Manager (including \"Allow APP configuration\"). The Admin UI, used by the same user on the same account/workspace, saves settings successfully. This is not a misconfigured role — no resource currently exposed in License Manager grants the permission the CLI's direct write path requires.\n\n## Simulation\n\n- As a user with the account's highest configured role (including \"Allow APP configuration\" checked, under Infrastructure resources), run: `vtex settings set vtex.store <field> <value>`.\n- Observe a 403 response: `Role User:<user> in <account>/ cannot perform action PUT on resource vrn:apps:...:/apps/vtex.store/settings`.\n- Confirm the same field can be saved successfully via `/admin/cms/store` or `/admin/apps/vtex.store@.../setup` by the same user, same account/workspace.\n\n## Workaround\n\nConfigure app settings via the Admin UI (`/admin/cms/store` or `/admin/apps/{app}@{version}/setup`) instead of the CLI."}