> 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.md). # Split Parts The **Split Parts** feature allows users to divide wall layers into smaller segments based on a predefined **Configuration**. This tool provides precise control over how wall layers are split, enabling advanced detailing, scheduling, or fabrication workflows. {% hint style="info" %} **Note:** *In order to see parts, switch on **Show Parts** or **Show Both** under **Parts Visibility** in the **View Properties**.* {% endhint %}


Workflow	Split Parts - Workflow
Configuration	Configuration
Modify Part	Modify Part
Reset All Parts	Reset All Parts
Show Identical Walls	Show Identical Walls
Copy Parts To All Identical Walls	Copy Parts To All Identical Walls
Copy Parts in Selected Identical Walls	Copy Parts in Selected Identical Walls

--- # 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.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.