> For the complete documentation index, see [llms.txt](https://wiki.mksdtech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.mksdtech.com/beam/beam-for-rhinoceros/levels.md).

# Levels

In Rhino, **levels** can be created and managed directly through the BEAM panel. A level represents a horizontal reference plane used to organize elements by height, similar to levels in Revit. Each level is defined by a name and an elevation in the Rhino model units.

When exporting from Rhino, BEAM assigns geometry to levels differently depending on the target format.

{% hint style="success" %}
In BEAM, IFC uses levels for all geometry (blocks and loose), while Revit only assigns levels to blocks, matching them by name or finding the closest level automatically.
{% endhint %}

For **IFC**, both blocks and loose geometry are always linked to a level. If a level is explicitly set in BEAM, that level is used. If set to automatic, BEAM finds the closest level below the object: for blocks this is based on the insertion point, while for loose geometry it is based on the bottom corner of the bounding box.

For **Revit**, only blocks are assigned to levels. Either the assigned level is used, or, if set to automatic, the nearest level below the block insertion point is chosen. In this case, BEAM matches levels by name, so the Rhino level name must correspond to a level already present in the Revit model.

<figure><img src="/files/dV5WsLefrcN5zBJ9Ajql" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/3VkMu2RXkUVzjaODsNbV" alt=""><figcaption></figcaption></figure>


---

# 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://wiki.mksdtech.com/beam/beam-for-rhinoceros/levels.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.
