> 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/3d-modeling-and-design/precast-concrete/feature-descriptions/beam-reinforcement/link-beam.md).
# Link Beam
This command links Rebar Configuration with selected Structural Framing Type. Choose which configuration should be used on each Type.
There are two ways how rebar configurations can be linked to a beam type.
***
### Option 1:
1. Create Rebar Configuration.
2. Select Structural Framing element in the model and click **Link Beam**.
3. In the following dialog window, assign configuration for each Type which should be reinforced.
Now you can use the **Create Rebar** command for this Structural Framing Type, which already has configurations assigned through the Beam Link.
***
### Option 2
1. Open Beam Configuration window.
2. Open the **Link Beam** tab.
3. Assign the configuration to the **beam type.**
4. Click **Save** at the bottom of the Configuration window.
***
{% hint style="info" %}
**Difference between Save (1) and Save (2) (for clearance – see image below):**
* **Save (1):** Saves only the configuration.
* **Save (2):** Saves both the configuration and any changes made within the **Link Beam** tab.
{% endhint %}
---
# 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/3d-modeling-and-design/precast-concrete/feature-descriptions/beam-reinforcement/link-beam.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.
