> For the complete documentation index, see [llms.txt](https://docs.anedot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.anedot.com/action-pages/page-builder/presets-in-the-page-builder.md).

# Presets in the Page Builder

Save a page's form, receipt, or settings as a preset in the Anedot Page Builder, update it for every page that uses it, and apply it to more Action Pages.

A **preset** is a named setup you can share across Action Pages. When several pages use the same preset, you can update it once and every page that uses it changes. The **Form**, **Receipt**, and **Settings** panels in the Page Builder have presets, and **Abandoned Actions** and **Pre-conversion upsell** let you reuse saved messages. Presets are available on Donation Pages, Event Pages, and Lead Pages. This article covers how to save, update, and apply presets.

## Before You Begin

* To save or apply presets, you need **Action Pages: Edit permissions**.
* Every account has a form preset named **Default**. New pages start on it.

## What Each Preset Saves

| Panel        | Where to Find It     | What the Preset Saves                                                                  |
| ------------ | -------------------- | -------------------------------------------------------------------------------------- |
| **Form**     | **Page > Form**      | The page's form settings, including every custom field position and hidden field value |
| **Receipt**  | **Setup > Receipt**  | The page's receipt settings: sender, subject, message, and logo                        |
| **Settings** | **Setup > Settings** | The page's tracking codes, pixels, and custom CSS                                      |

{% hint style="warning" %}
**Save as Preset**, **Update Preset**, and **Apply to pages…** take effect right away, without clicking **Save**. Updating a preset also updates every page that uses it.
{% endhint %}

## Save a New Preset

To save a page's setup as a new preset:

1. Go to **Action Pages > Pages**.
2. Click the name of the page you want to edit.
3. Open the **Form**, **Receipt**, or **Settings** panel.
4. Click **Save as Preset**.
5. Enter a **Preset Name**.
6. Click **Save as Preset**.
7. Click **Save** to attach this page to the new preset.

## Update a Preset

If a page uses a shared preset and you've changed the panel, you can update the preset itself.

1. Make your changes in the **Form**, **Receipt**, or **Settings** panel.
2. Click **Update Preset**.
3. Review the warning, which shows how many Action Pages use the preset.
4. Click **Update Preset**.

**Update Preset** only appears when the page uses a shared preset and has unsaved changes in that panel.

{% hint style="info" %}
If you change a panel on a page that uses a shared preset and click **Save** instead of **Update Preset**, only that page changes. The page gets its own copy of the settings and stops following the preset.
{% endhint %}

## Apply a Preset to Pages

To put more pages on a preset:

1. Open the **Form**, **Receipt**, or **Settings** panel on a page that uses the preset.
2. Click **Apply to pages…**.
3. Check the pages you want to put on the preset, or check **All Pages**. Pages already on the preset show an **On this preset** badge.
4. Click **Apply**.

### Take Pages Off a Form Preset

In the **Form** panel, you can also take pages off a preset. In **Apply to pages…**, uncheck a page that shows **On this preset**. The badge changes to **Coming off**. When you click **Apply**, each page you unchecked keeps the form it has today as its own settings and stops following the preset.

Receipt and Settings presets can't take pages off from this list.

{% hint style="info" %}
When you apply a form preset, the list shows only pages that can use it. A Lead Page's form preset can go on Lead Pages. A Donation Page's or Event Page's form preset can go on Donation Pages and Event Pages.
{% endhint %}

## Reuse Saved Messages in Workflows

**Abandoned Actions** and **Pre-conversion upsell** have a **Preset** field. Use it to pick a message you've saved before, or save the fields as a new preset. To learn more, see [Abandoned Actions](/action-pages/page-builder/abandoned-actions.md) and [Upsells and Upgrades](/action-pages/page-builder/upsells-and-upgrades.md).

## Related Articles

* [Page Builder Overview](/action-pages/page-builder.md)
* [Custom Form Fields](/action-pages/page-builder/custom-form-fields.md)
* [Hidden Fields](/action-pages/page-builder/hidden-fields.md)
* [Receipts and Confirmation Page](/action-pages/page-builder/receipts-and-confirmation-page.md)
* [Page Settings: SEO, Sharing, and Tracking](/action-pages/page-builder/page-settings-seo-sharing-and-tracking.md)


---

# 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.anedot.com/action-pages/page-builder/presets-in-the-page-builder.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.