> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/equipme/controlling/orders.md).
# Orders
The order overview lists everything your organisation has ordered, with the current state of each order and the people involved in it.
### Requester, purchaser and recipient are three different people
An order often passes through more than one pair of hands. An employee submits a request in Self Service, a manager places the order, and the device ends up with a third person. Or an administrator creates a request on behalf of someone else entirely.
The overview keeps these roles apart:
* **Requester** — who originally submitted the request
* the person who **placed the order**
* the employee the product or service was **assigned to**
The Requester column in the order overview.
The requester is recorded when the order is created and stays with the order from then on. You do not have to go back to the original order request to find out who started it — which is what makes follow-up questions answerable weeks later, when nobody remembers who asked for what.
In approval and ordering workflows with several people involved, this keeps responsibility traceable without anyone having to document it by hand.
---
# 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://hub.equipme.io/equipme/controlling/orders.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.
