> For the complete documentation index, see [llms.txt](https://docs.maitredpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-4-point-of-sale-control/help-contents/screens/preferential-screen-setup/button-layout.md).

# Button Layout

**Button Layout**

**Button Appearance**

**Screen color**

Choose an item from the list. To know about screen colors available, please refer to the POS Screen designer document available on Posera web site.

**Graphic**

Choose a graphic type from the list by clicking on the scroll button . To know about graphic type available, please refer to the POS Screen designer document available on the Posera web site.

**3D Border**

Enable this option to display a three dimensional border to the key.

**Option**

**Bottom expand**

Select this to expand the key size including the bottom key space. If there is no key available underneath it (you are editing a key from the last row), the field wont be available.

**Right expand**

Select this to expand the key size including the right key space. If there is not key available on the right (you are editing a key of the most right column), this field wont be available.


---

# 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.maitredpos.com/maitred/maitred-complete-online-documentation/chap-4-point-of-sale-control/help-contents/screens/preferential-screen-setup/button-layout.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.