> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pba-ctools/10.2-ctools/cde-dashboard-overview/community-dashboard-editor-cde-perspectives-ctools/components-perspective-ctools-cde/adding-and-setting-up-components.md).

# Adding and setting up components

You can add components to your dashboard and customize them.

1. From the Components perspective, in the left menu, expand the category where your component belongs.

   For example, if you want to add a date input component, expand the **Selects** category.
2. Select the component you want to add, such as **Date input Component**.

   The new component will be added to the **Components** pane in the middle of the screen.
3. Select the component in the **Components** pane to customize it in the **Properties** pane on the right.

   ![Customizing a component from the Properties pane](/files/997RoexS52GmDUeufocG)

   For each component, there is a list of basic and advanced properties which you can set to define the component.


---

# 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.pentaho.com/pba-ctools/10.2-ctools/cde-dashboard-overview/community-dashboard-editor-cde-perspectives-ctools/components-perspective-ctools-cde/adding-and-setting-up-components.md?ask=<question>&goal=<endgoal>
```

`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.