> 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/3d-modeling-and-design/clt-panels/elements/configuration-window.md).

# Configuration Window

![](https://239424168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqtUsszuAWXIZhQhrvjnb%2Fuploads%2Ft2YamSkg22JkaLN8Byew%2F0.jpeg?alt=media)

In the Configuration window you can define settings for how Line-based and Point-based Families should be placed on the Host. Configurations are saved in your computer. Location of files is defined in Configuration Files' Location. Configurations can be created once and be used in any future projects.

1. Select category of Host element.
2. Assign Configuration to selected Group.
3. Save, Rename, Duplicate, Create new configurations here.
4. Hide Line-based Details, Hide Unused Tree Nodes. (self-explanatory)
5. Choose appropriate tab to insert Line-based or Point-based Families on selected faces. You can drag-and-drop a selected element to change its position. Software inserts elements starting from first tab at the top.
6. Detail priority tabs - here you can define rules for how selected Families can be distributed on Host elements.
7. Configuration Group - here you can manage configuration groups.

![](https://239424168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqtUsszuAWXIZhQhrvjnb%2Fuploads%2F5mPm8kmvUPRFGSVuiuZV%2F2.png?alt=media)


---

# 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/3d-modeling-and-design/clt-panels/elements/configuration-window.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.