> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/collect-data/shopify/support-access.md).

# Support access

We recommend every Shopify store gives Chord's support team staff access, through the account `access@chord.co`. With it, Chord can look at your pixel, apps and settings directly when you need help, instead of working from screenshots.

This is optional. You set up Chord yourself either way.

## Step 1: Create a store role for Chord

1. Sign in to Shopify admin as a store owner or admin.
2. Go to **Users > Roles** and click **Add role**.
3. Create the role under the **Store** category, and name it however you like, for example "Chord support".
4. Give the role these permissions. Anything not listed isn't needed.
   * **Orders:** View; Cancel; Returns and refunds (Return, Refund to original payment, Refund to store credit)
   * **Drafts:** View
   * **Products:** View, including View cost
   * **Gift cards:** View; Create and edit
   * **Customers:** View
   * **Marketing:** View, create and delete marketing activities and automations; Campaigns (View, Create and edit, Delete)
   * **Discounts:** View, create and delete
   * **Content:** Files (View, Create, Edit, Delete)
   * **Finance:** View Shopify Payments payouts
   * **Analytics:** Reports; Dashboards
   * **Online Store:** Themes (Edit code, including generating theme blocks); Blog posts and pages
   * **App development:** View apps developed by staff and collaborators (Develop, Enable development)
   * **Store settings:** Manage settings; Locations; View customer events (Manage and add custom pixels)
   * **App and sales channel permissions:** Manage and install apps and channels
5. Add `access@chord.co` as a staff member with this role.

## Step 2: Give Chord the App Developer role

Also give `access@chord.co` the **App Developer** role under the **Organization role** category. It's a default role, so you don't need to create it. It lets Chord see the Chord Webhook Events and Chord Data Ingestor apps in the Dev Dashboard when troubleshooting.

Let Chord know when both steps are done.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.chord.co/collect-data/shopify/support-access.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.