> For the complete documentation index, see [llms.txt](https://uxsmart.gitbook.io/velare/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://uxsmart.gitbook.io/velare/help-and-faqs/staff-account.md).
# How do I give the support team access to my store?
### What you are seeing
You reported a problem with the theme, and support asked for a staff account on your store. You want to know why, what they will be able to see, and how to give access safely.
### Why support asks for it
Screenshots show what a problem looks like, not what is causing it. A staff account lets our developers open your theme editor and your theme settings and fix the issue directly, instead of sending you a list of things to try one at a time. It is the fastest route for anything that cannot be reproduced on a demo store.
You stay in control. A staff account is created by you, uses permissions you choose, and can be removed by you at any time.
### How to create the staff account
{% hint style="success" %}
**Steps:**
1. Follow Shopify's guide on [adding and managing staff](https://help.shopify.com/en/manual/your-account/staff-accounts) to send the invitation.
2. Send the invitation to
3. Give the account permission to work on the theme, so the developer can open **Online Store > Themes** and the theme editor.
4. Tell support once the invitation is sent, so they can accept it.
{% endhint %}
*Result:* our developers can open your store, reproduce the issue on your own theme, and apply the fix.
{% hint style="info" %}
Remove the staff account once your issue is closed. In your Shopify admin, open the staff list, select the account and remove it. You can invite it again the next time you need help.
{% endhint %}
### What to send along with the access
Access alone is not enough. Support still needs to know what to look at, so include this in the same message:
* Your store URL, and the URL of the page where the problem appears.
* A screenshot or a short screen recording of what you see, and what you expected instead.
* The steps that reproduce it, and whether it happens on desktop, on mobile, or both.
* Theme name and version: **Vélare 1.0.0**, shown under the theme name in **Online Store > Themes**.
* Any custom code you added, and any app that touches the same area of the store.
### Related pages
* [How to change Elements of page?](/velare/help-and-faqs/how-to-change-elements-of-page.md): find the section behind the problem before you report it
* [Custom CSS](/velare/customize-your-pages/custom-css.md): custom code is the first thing support will ask about
* [Theme translation](/velare/help-and-faqs/theme-translation.md): another area where a staff account speeds things up
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://uxsmart.gitbook.io/velare/help-and-faqs/staff-account.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.