For example, I have a Shopify Plus Organization that installed my app across 8 stores. These stores have 3 different emails under shop.email in GraphQL, even though shop.shopOwnerName is the same across all 8 stores - and the organization owner only has one Shopify account with a single email associated with it.
I was hoping to properly identify organizations when I discovered the shop.accountOwner field in GraphQL. Unfortunately, this field requires the read_users scope, which isn’t available for public apps as far as I know.
I’m not sure if this is an oversight, but I wanted to request whether it might be possible to expose shop.accountOwner without requiring the read_users scope. This would significantly simplify recognizing Shopify Plus Organizations and determining the best way to contact account owners.
The only method I’ve found of correctly identifying the account owner’s email is through an online access token.
But that requires them to login to the app.
If your app relies on usage charges, you’ll have to send notifications to staff to let them know their cap is close to exhausted, but those emails can be lost if they go to the general shop.email inbox which also might be used for end customer support.
Hey Dylan, yeah I use online access token now, which makes me think that perhaps restricting shop.accountOwner is an oversight.
Problem with online access token is that not only do they have to open the app, but also the account owner can change, so if the owner changes or they change their email and do not log into the app after, you won’t know
