> For the complete documentation index, see [llms.txt](https://docs-en.shoppy.is/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-en.shoppy.is/shoppy-dashboard/settings/account.md).

# Account

### &#x20;**Account overview**

Here you can see your Shoppy account information:

* **Store name**: the name of your store
* **ID**: identifier of your Shoppy account
* **Email**: your email address, which we will use to send you all communications about Shoppy
* **Time zone**: your time zone, which is used when you need to schedule news or push notifications.

![](https://2580671618-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJPDzUzynACRbcxkhAEeE%2Fuploads%2FbvGxIZBy0cniQFmk7UtM%2FSchermata%202022-04-15%20alle%2015.36.19.png?alt=media\&token=a01349b5-2ed6-4f11-b0e9-190b5557ee26)


---

# 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-en.shoppy.is/shoppy-dashboard/settings/account.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.
