> 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-views/workflow.md).
# Workflow
{% hint style="warning" %}
This page is under reconstruction
{% endhint %}
**Smart Views** creates views of selected elements and dimensions anything that is visible in those views, as needed.
**Workflow**
1. **Create Smart Views configuration**
Select views that should be created and templates that should be applied to them:
2. **Create Smart Dimensions and Smart Tags configurations**
Once you have set your configurations in Smart Dimensions and Smart Tags, assign them to selected views.
Example:
3. **Define how views should be named**
4. **Save configuration**
5. **Select element(s) in the model for which views should be created**
Click 'Create views'. Views for selected elements will be created based on the most recently opened Smart Views configuration.
For example, a configuration has one Front view selected. I have selected 3 walls, so a Front view for each wall is created.
Front views of the walls with dimensions created:
Or select **Multiple Elements** > **Create View**. In this case, views will be cropped to the boundary defined by selected elements:
---
# 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-views/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.