> 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/smart-connections/configuration-window/detail.md). # Detail

**Select Category** - select category of Families you want to insert. Possible Categories - Smart Connections, Structural Framing, Generic Model. Only selected Category elements will be available in the drop-down window below. **Family and Type Browser** - opens window for easy visual selection of elements you want to insert. It will filter out all Point-based or Line-based families, depending on which tab you are in.

Or you can select an element from the drop-down menu.

**Host filter** - additional option to to apply additional filters for the host. **Line-Based Element Direction -** enables changing the direction of line-based families on the host face.

**Cut Geometry** - allows you to cut Host element if you have a void inside of your detail Family.\ **Join Geometry** - allows you to join Host element with detail Family.

Elements can be inserted on one side or several sides; select option from the table:

--- # 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/smart-connections/configuration-window/detail.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.