> For the complete documentation index, see [llms.txt](https://docs.aquiladynamics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aquiladynamics.com/aquila-store-user-manual/getting-started/changing-work-location.md).
# Changing work location
## Changing work location
During one session, a user can view documents and perform operations for different locations, provided that the user has access to them.
**Menu path:** `Application -> Location change`
### When to use
Use this function when you want to work with data of another store, head office or another location available to your account.
### Selecting an existing location
1. Open `Application`.
2. Select `Location change`.
3. On the `Location selection` screen, find the correct location.
4. If needed, use `Filter` to narrow the list.
5. Select the location.
6. Click `SELECT` to start working in the selected location.
### What to watch for
* Changing location affects the visibility of documents, reports, warehouses and some operational data.
* If the user cannot see a location, check permissions or location assignment.
* After changing location, make sure that the correct location is visible in the upper-right corner of the system.
### Related pages
* [Logging in](/aquila-store-user-manual/getting-started/logging-in.md)
* [User roles in the system](/aquila-store-user-manual/introduction/user-roles-in-the-system.md)
---
# 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.aquiladynamics.com/aquila-store-user-manual/getting-started/changing-work-location.md?ask=&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.
