> This page is for Developer.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.bigcommerce.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.bigcommerce.com/_mcp/server.

## Control Panel users can use metafield and EventBridge GraphQL fields with store permissions

Control Panel users who are not the store owner can now use several Admin GraphQL fields when they hold the matching store permission; until now these fields answered `You do not have permission to do this operation` for every user except the store owner. Access with API account tokens is unchanged.

* **Single metafield lookups:** the `metafield` query on `store` accepts any metafield read permission, such as Manage Products, Manage Orders, Manage Customers or Manage Settings. We are beginning to restrict these reads to the resource types the user's permissions cover, matching the existing `metafields` list query; you may notice this over the coming weeks. Once restricted, a user with Manage Orders can read order metafields but not product metafields.
* **Deleting metafields:** the `deleteMetafield` mutation accepts the Manage Settings permission, the same permission `createMetafield` and `updateMetafield` already accept.
* **Amazon EventBridge event sources:** the `eventSources` query on `store` accepts List Store API Tokens, `createEventSource` accepts Create Store API Tokens, and `deleteEventSource` accepts Delete Store API Tokens. These are the permissions that gate the Store API Accounts area of the control panel, so users who manage API accounts can now manage EventBridge event sources there too.
* **Reassigning metafield owners:** the `reassignMetafieldsOwner` mutation still requires the `store_metafield_change_owner` scope for API accounts and additionally accepts Control Panel users holding Grant High-Risk Store Permissions.
* **Unchanged:** API account tokens keep the same OAuth scope requirements and the GraphQL schema does not change.

For details, see [Metafields](/developer/docs/integrations/metafields) and [Amazon EventBridge](/developer/docs/integrations/webhooks/aws-eventbridge).