> 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/split-parts/split-parts-workflow.md).
# Split Parts - Workflow
In order to see parts, switch on **Show Parts** or **Show Both** under **Parts Visibility** in the **View Properties***.*
1. The **Split Parts** command can be executed in **two ways**:
1. **Select a Wall (or Part) First**
* The user selects a wall or specific wall layer directly in the model.
* Then, the **Split Parts** command is activated.
*
2. **Select the Command First**
* The user activates the **Split Parts** command from the toolbar or menu.
* The system enters *selection mode*, prompting the user to pick a wall or part (layer) in the model.
2. After completing the first two steps using either method, a pop-up window appears where you can select a predefined configuration for each wall layer. Learn how to create a configuration [here](https://app.gitbook.com/o/GVtnSLEqyn4gTgkVXno7/s/qtUsszuAWXIZhQhrvjnb/~/changes/1669/3d-modeling-and-design/smart-connections/split-parts/configuration).
Wall before splitting
Insulation after splitting
---
# 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/split-parts/split-parts-workflow.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.
