> For the complete documentation index, see [llms.txt](https://academy.any2info.com/any2info-academy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.any2info.com/any2info-academy/no-code-platform/app-studio/application-design/dashboard/controls-toolbox/general/controls-properties.md).

# Properties

Add properties to dashboard controls

### **Properties**

When you select a control on the canvas, the **right sidebar** will show the specific **component properties** panel. There you can set what kind of data and other content your UI components display, configure how they function and define how they are bound to app data. 

<div align="left"><figure><img src="https://870194474-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_kE41Rl4pOtwKfvvQq%2Fuploads%2FN6duB2TnF2gzAH2MYLB8%2FToolbar%20dashboard%20control.png?alt=media&amp;token=db8d778b-189a-48fe-9fc0-7779c08f56f3" alt=""><figcaption></figcaption></figure></div>

**Property General - Use of display texts:** You can add a display text to a component. Alle display texts are accessable in the menu part [**Translations**](/any2info-academy/no-code-platform/tools/translation.md). There you also can add different languages for  the display texts.

#### Docking

Each control can be docked into position on the screen for:

* height and width&#x20;
* distance to top, bottom, left side and right side

Depending the docking and the set scale mode a control wil scale with the size of the device or has a fixed size.

<div align="left"><figure><img src="https://870194474-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_kE41Rl4pOtwKfvvQq%2Fuploads%2FrZJFYIYVlwENmcJc2bB6%2FImage%20docking.png?alt=media&amp;token=730371f5-cf61-466f-b313-a6140318b280" alt=""><figcaption></figcaption></figure></div>

### [**Styling**](/any2info-academy/no-code-platform/app-studio/designertools/stylesheets.md)

**Property Text -  Use of placeholder text**&#x20;

To some of the form fields a specific placeholder text can be added.

### [**Events**](/any2info-academy/no-code-platform/app-studio/application-design/dashboard/controls-toolbox/general/events-actions.md)

A wide range of controls have the possibility to set an event, for example on a click, update or value change.&#x20;

Selecting the control on the canvas will open the right bar panel where you can add events.

### [**Links**](/any2info-academy/no-code-platform/app-studio/app-logic/dashboards/dashboard-links.md)&#x20;

On a dashboard page you can link specific controls, and their specific data, to other controls.&#x20;

For example:&#x20;

* A bar graph has to be linked to a selection of items in a dropdown control.&#x20;
* Date time fields (from - to) are linked to a grid overview

All links are created by using the properties of an available data clip. These properties can be selected and mapped in the relevant data clip. See the section [**Mapping controls**](/any2info-academy/no-code-platform/app-studio/data/mapping-dashboard-data.md).

###


---

# 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://academy.any2info.com/any2info-academy/no-code-platform/app-studio/application-design/dashboard/controls-toolbox/general/controls-properties.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.