> 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/common-for-several-products/smart-assemblies/shop-drawing-configurations/insert-grid-lines.md).

# Insert Grid Lines

![](/files/wPO34ixHg3TSmZCC0XUH)

If this option is checked and a grid is crossing the Assembly in the project, then Smart Assemblies will create a 2D family to represent the grid in the Assembly view.

### **Example**

Walls are crossed by grid lines in the model. This is a plan view of Level 1:

![](/files/FygKJLPJKhFoHyZHqaHU)

If we create an assembly with the **Insert Grids** option turned ON, then **Dimension** will also be turned ON in the Dimensioning Rules:

![](/files/co607YDh7dNDHw7Q2704)

After the Assembly has been created, you will get these results:

Front View - you can see a gridline 2D Family inserted with some available parameters and also the dimension line, in this case, from the grid to the wall.

![](/files/Ca9Ap0XTTb3dgqOtEdbc)

Top View:

![](/files/IyDFayFu2LDGk4copK0z)

You can modify the gridline family and use this option with different Categories, like columns, beams, etc. Here is an example of a column in the plan view:

![](/files/tPeliMrs8MMBJBUz7wIt)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.besmart.software/common-for-several-products/smart-assemblies/shop-drawing-configurations/insert-grid-lines.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.