> For the complete documentation index, see [llms.txt](https://docs.funnelish.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.funnelish.com/start/funnel-builder/saving-assets.md).
# Saving assets
You can easily **save elements, rows or sections to use across all your funnels.** This is possible with our **Save as asset** feature, that will store and organize the designs you choose.
Assets.
## Save a design as an asset
1. **Click** once on the **section, row, element or container** that holds your design.
A blue outline will highlight what you are about to save as an asset.
2. Click on the **Save as asset** icon located in the top right corner of the **settings panel**.
Save as Asset.
2. On the pop-up window, select the folder where you want to save your asset or create a new one by clicking on the plus (+) icon.
3. Give a name to identify your asset, and click **Create asset**.
Creating Asset
{% hint style="success" %}
Now you **can access your saved assets in any of your funnels using the panel at the left of your canvas.**
{% 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 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.funnelish.com/start/funnel-builder/saving-assets.md?ask=&goal=
```
`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.