> For the complete documentation index, see [llms.txt](https://docs.besmart.software/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.besmart.software/common-for-several-products/smart-dimensions/configuration-window.md).
# Configuration Window
Configuration window
1. \- Select, Create, Duplicate, Rename, Save your configurations
2. \- Select Category of elements that you want to dimension with that configuration in the View. Order of Categories defines which dimension Line will be the first dimension line. You can drag & drop selected categories up and down.
3. \- Common Settings - define how dimensions should be grouped, joined, and what Filters should be applied
4. \- Text Note Settings - define the format of text notes for dimensions
5. \- Select one of the orientation/position tabs to define rules for how to dimension elements in the View. Depending on the category, there will be a different number of tabs for dimensioning. If the Tab name has **green** color - it means there are settings for dimensioning turned on.
6. \- Dimension 1,2,3...10 - it's possible to add more tabs and apply different filters, dimension styles for different elements to dimension.
7. \- Add/remove Dimension tabs. Symbol "+" will create a duplicate of the active Dimension tab with all its settings.
8. \- Define settings for total dimension, diagonal dimension, linked elements measuring, first line offset etc.
---
# 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.besmart.software/common-for-several-products/smart-dimensions/configuration-window.md?ask=&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.