> 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/help-contents/employees/screen-access/screen-access-setup.md).

# Screen Access Setup

### Employees

#### Screen Access

Screen Access Setup is used to determine which POS employees have access to which preferential screens depending on their functions. The Screen Access Setup tool allows access to preferential screens to be configured individually for each Revenue Center and Mode combination.

***

### **Description**

Type in a meaningful description for this screen access configuration. This field supports up to 20 characters. Since Screen Access Configurations will be assigned to employees, it is good practice (but not mandatory) to name each Screen Access Configurations in such a way that they can be easily related to the employee job function they are intended to. For example, the Screen Access Configuration intended for Bartenders could be named “A.Bartenders”.

**Floor Plan**

Select the floor plan to be associated with this screen access. Select the Default option to let the POS workstation decide which floor plan to use.


---

# 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-4-point-of-sale-control/help-contents/employees/screen-access/screen-access-setup.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.