> For the complete documentation index, see [llms.txt](https://docs.payfacto.com/payfacto-knowledge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payfacto.com/payfacto-knowledge/maitred-pos/maitred/maitred-complete-online-documentation/chap-7-server-control/workstation.md).

# Workstation

<details>

<summary>Make Data</summary>

#### -Make Data

This option will prepare on your hard disk the data needed by all the workstations in order to take the information each workstation need to work properly.

**-All workstations**

Enable this option to create data directories for all your workstations.

**-Workstation number**

Enable this option to select from the drop-down menu the workstation number for which you want to create data directory.

To accept this message, press ENTER or click on OK.

**-Data Only**

Enable this option to create workstation data only, without copying the executables.

</details>

<details>

<summary>Local Workstation Data</summary>

Select this option to create workstation data for the local workstation only.

</details>

<details>

<summary>All Workstation Data</summary>

Select this option to create workstation data for all workstations.

</details>

<details>

<summary>Close All Workstations</summary>

Select this option to stop the Point of Sale application on all workstations at once.

<br>

</details>

[Back to top](#make-data)


---

# 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.payfacto.com/payfacto-knowledge/maitred-pos/maitred/maitred-complete-online-documentation/chap-7-server-control/workstation.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.