> 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/how-to-add-legends-to-assembly-sheets.md).

# How to Add Legends to Assembly Sheets

Smart Assemblies allows you to automatically place Legends on Assembly Sheets.

Legends are Views, but in Revit, these Views cannot be created as separate Assembly Views.

To add Legends to your Assembly sheet, you need to drag them from the Project Browser and place them on the Assembly sheet.

**Workflow**

1. In the Shop Drawings Configuration window, add a view and select it to be a Legend.
2. In the View Template column, select which Legend you want to create for Assemblies with this configuration.

   ![](/files/onzooDwaAf9b3UOwcxKL)
3. Create the Smart Assembly.
4. Drag views to the Assembly Sheet.
5. Drag Legends to the Assembly Sheet.
6. Return to the Shop Drawings Configuration and select this Sheet to be a Sheet Template.

   ![](/files/K0nCXs9aj7N1HBqgDQcb)
7. Now create other Assemblies using this Configuration.

All these new Assemblies will have Legends placed on the Sheet automatically at the same location as in the Sheet Template.

![](/files/8VDEg9p3ghjVvoF0BQLc)


---

# 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/how-to-add-legends-to-assembly-sheets.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.