> For the complete documentation index, see [llms.txt](https://docs.beefree.io/end-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.beefree.io/end-user-guide/reuse-content/saved-rows.md).

# Saved Rows

### What Are Saved Rows?

Saved rows are pre-configured sections of design that you can store for future use in the builder. These rows could contain a variety of elements like text, images, or buttons, arranged in a specific way. They're a shortcut for adding complex structures you plan to reuse.<br>

<figure><img src="https://lh7-eu.googleusercontent.com/WLMQsRxYfUfl-JuJijgJv0467Xgj7ltzbhAlddx7UUSZZEM3UFxm3gvbJFF_vcSB4mnBbqYDci5A95wuAHPU64pWltx7rZr7QQPNyAj11NgGNaldiK7B-AATcFegwQ-IEyRUlfJehLfDsP2RqPHof24" alt=""><figcaption></figcaption></figure>

<figure><img src="https://lh7-eu.googleusercontent.com/hhWLZR4TXiXj6J3p7OJwOab7dIIGBZZpSijDdcD9zxziahF4UhKI8aXCRll94HZjnHa1hgWBgPf8EhbAXdvHO5zfKqNk2d5_jPBx0NedJmOA-gmlMbQq6dWMqhd2D-HIrZ9HB-CN6U8AiwwK68I70Jg" alt=""><figcaption></figcaption></figure>

Key Characteristics:

* Reusability: Once saved, these rows can be dragged and dropped into any new or existing design.
* Customization: Even after a row is saved, it can be modified without affecting its original version.
* Flexibility: Saved rows make it easy to maintain consistency across various projects while still offering room for project-specific tweaks.

### How to Manage Saved Rows

* Update: You can change the content or settings of a saved row at any time. This won't affect the places it's already been used.
* Edit Details: Change the name or category directly from the builder sidebar.
* Delete: Remove a saved row if it's no longer needed.

Using saved rows effectively can speed up your workflow, help maintain design consistency, and allow for greater creative flexibility.

<br>


---

# 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.beefree.io/end-user-guide/reuse-content/saved-rows.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.
