> 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/dimensioning-rules/smart-dimensions.md).

# Smart Dimensions

Here you can access Smart Dimensions Configurations.

The checkbox allows you to select Smart Dimensions Configuration which should be used together with Dimensioning Rules.

{% hint style="info" %}
It's recommended to use Main Element Geometry tab to dimension cuts and openings and use Smart Dimensions for everything else.

Read more about Smart Dimensions configurations [**here**](/common-for-several-products/smart-dimensions.md).
{% endhint %}

**Edit** - opens configuration window of Smart Dimensions.

![](https://239424168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqtUsszuAWXIZhQhrvjnb%2Fuploads%2Fm7rz1VoouKvwXlRpdUe4%2F0.jpeg?alt=media)

{% hint style="info" %}
If you want to use Smart Dimensions, make sure it is also turned ON in the 'Dimensioning Priority & Notes' tab:
{% endhint %}

![](https://239424168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqtUsszuAWXIZhQhrvjnb%2Fuploads%2FCyoY0JWYP7OVk45ZnNiL%2F1.jpeg?alt=media)


---

# 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/common-for-several-products/smart-assemblies/dimensioning-rules/smart-dimensions.md?ask=<question>&goal=<user_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.