> 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/access-to-revenue-centers.md).

# Access to Revenue Centers

### Screen Access

**Revenue Center Names**

All the Revenue Centers are listed on the left-hand side of the window. Screen access needs to be configured for each individual Revenue Center. Click on a revenue center to configure screen access for it.

**Default Mode**

Select the default mode to be used with this screen access configuration. Select the Regular option to let the POS workstation decide what the default mode should be.

{% hint style="info" %}
NOTE: The default mode for workstations is configured in Point of Sale Control / Workstation / Options / Workstation.
{% endhint %}

**Show Selection**

Enable this option to make the selected Revenue Center available with this Screen Access configuration.

**Modes**

This area lists available modes for the selected Revenue Center. Click on a mode to configure its screen access.

**Default**

Select the default preferential screen to be used with the selected mode in this screen access configuration. This is the first screen that the employees will see after they login to the POS workstation.

**Preferential Screens**

This list provides individual checkboxes for each preferential screen. Tick every screen which should be accessible from this Screen Access configuration. A ticked box means that the employee will have access to that preferential screen in the selected revenue center and mode.

**Select All**

![Button - Select All](https://documentation.payfacto.com/POS/MaitreD/Fulldoc/assets/images/MaitreDCommon/Buttons/MDButton-SelectAll\(LONG\).jpg)

Click this button to enable all preferential screens in that mode.

**Clear All**

![Button - Clear All](https://documentation.payfacto.com/POS/MaitreD/Fulldoc/assets/images/MaitreDCommon/Buttons/MDButton-ClearAll\(LONG\).jpg)

Click this button to disable all preferential screens in that mode.

**Copy To**

![Button - Copy To](https://documentation.payfacto.com/POS/MaitreD/Fulldoc/assets/images/MaitreDCommon/Buttons/MDButton-CopyTo-LONG.jpg)

Click this button to open a window to choose multiple target modes to copy preferential screen accesses.

**Copy To All**

![Button - Copy to All](https://documentation.payfacto.com/POS/MaitreD/Fulldoc/assets/images/MaitreDCommon/Buttons/MDButton-CopytoAll-LONG.jpg)

Click this button to copy the current preferential screen accesses to all modes.

**Previous**

![Button - Previous](https://documentation.payfacto.com/POS/MaitreD/Fulldoc/assets/images/MaitreDCommon/Buttons/MDButton-Previous\(LONG\).jpg)

Click this button to move up to the previous mode in the list.

**Next**

![Button - Next](https://documentation.payfacto.com/POS/MaitreD/Fulldoc/assets/images/MaitreDCommon/Buttons/MDButton-Next\(LONG\).jpg)

Click this button to move down to the next mode in the list.


---

# 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/access-to-revenue-centers.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.