Currently the StaffMember data cannot be accessed by public applications as the read_users scope can only be provided to private applications installed for Shopify plus or advanced customers. Would it be possible to provide access to the StaffMember id for public applications via the read_users scope or a new read_user_id scope? This would allow public applications to at least link other GraphQL entities like order and refund to a user id which the Shopify plus or advanced merchant can then identify via a separate private applications. This would avoid the requirements applications to have duplicate public and private versions without compromising on access to private data.
Also the StaffMember data can be accessed by “finance embedded app”. Could you please elaborate on how an application qualifies as finance embedded and what that means?
the StaffMember data cannot be accessed by public applications as the read_users scope can only be provided to private applications installed for Shopify plus or advanced customers
@Liam-Shopify no this is a separate issue. For the one you are referring to this is access with a private token and read_users scope. In the scenario I describe here we are using the public access token.