> 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-4-point-of-sale-control/screens/preferential-screens/preferential-screen-setup.md).
# Preferential Screen Setup
Preferential Screens are created to display a logical grouping of sales items. For example, a preferential screen can be created to display the selection of soft drinks available or a list of desserts. Preferential screens can also be modified on the fly.
Typically, a restaurant will have several preferential screens, which will be displayed depending on the time of day or the employee role. Bartenders will have access to different preferential screens than dining room servers. This gives restaurants a great amount of flexibility when customizing their POS workstation screens.
***
### Access Preferential Screen Setup
1. Logon to the Maitre’D Back-Office with appropriate credentials. (Distributor or System Owner)
2. Start the Point of Sale Control module.
3. Click on the Screens menu and select Preferential Screen setup...
4. The list of available Preferential Screens is displayed.
Select an existing preferential screen and click the Modify button to edit its properties.
Click the Add button to create a new preferential screen from scratch.
Click the Close button to exit the list and return to the Point of Sale Control module.
5. The Preferential Screen Editor will appear.
#### Preferential Screen Editor - Advanced POS UI
#### Preferential Screen Editor - Legacy POS UI
---
# 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://docs.payfacto.com/payfacto-knowledge/maitred-pos/maitred/maitred-complete-online-documentation/chap-4-point-of-sale-control/screens/preferential-screens/preferential-screen-setup.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.