> 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/adjust-layout-by-searching-for-other-elements/wall-joins.md).
# Wall Joins
**Wall Joins** - search for different intersection of Walls. Available if Category of Configuration is Wall. Possible options via Wall Joins:
1. End Connection - Places elements at the end connection of the wall that is connected to another wall (both start and end if the wall is connected from both sides).
2. End Connection End - Places elements at the end connection of the wall only on the End side.
3. End Connection Start - Places elements at the end connection of the wall only on the Start side.
4. Free - Places elements at the Free End and Free Start connection of the wall.
5. L Butt Connection - Places elements on the butted wall in an L connection.
6. L Connection - Places elements at the L connection (used for the long wall, not for the butted wall).
7. T Butt Connection - Places elements at the T connection on the butted wall in both End and Start side.
8. T Butt Connection End - Places elements at the T connection on the butted wall only on the End side.
9. T Butt Connection Start - Places elements at the T connection on the butted wall only on the Start side.
10. T Connection - Places elements on the wall in a T connection.
11. X Connection - Places elements at the X connection (when the wall has two connected walls at the same point from both sides).
**Part Joints** - search for different intersection of Parts.
---
# 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/adjust-layout-by-searching-for-other-elements/wall-joins.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.
