> 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-6-system-configuration/file.md).

# File

### Printer Setup

This option is driven by your Windows Ò operating system. This option enables to select the printer and parameters you wish to use to print your reports.

#### Print Last Report

This option gives you the option to see the last report you have requested and to reprint it if necessary.

***

### Log

The Log option allows to start and view operations traces about System Configuration Module. Three different Log level are available, Standard, Detail and Debug. This option is for trouble shooting purpose and should be use only with the supervision of your Maitre'D reseller.

**Log Level**

Three different Log level are available: Standard, Detail and Debug. This option is for troubleshooting purposes and should only be used with the supervision of a certified Maitre'D support specialist.

![Button - View](https://documentation.payfacto.com/POS/MaitreD/Fulldoc/assets/images/MaitreDCommon/Buttons/MDButton-View.gif)

Use the View key to access to log file.


---

# 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-6-system-configuration/file.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.