> ## Documentation Index
> Fetch the complete documentation index at: https://docs.conversion.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Creating and editing

> How Conversion AI creates new assets and proposes edits to existing ones, and how you approve them.

Conversion AI changes your workspace in two distinct flows, and they behave differently. **Creating** a new asset and **editing** one that already exists are not the same thing.

## Creating new assets

When you ask for a new email, form, or workflow, Conversion AI builds it and creates it **live but dormant** — as an unpublished draft:

| Asset                           | What "dormant" means                                                             |
| ------------------------------- | -------------------------------------------------------------------------------- |
| Email (blast or workflow email) | Created in **draft**. Nothing is sent or scheduled.                              |
| Email template                  | Saved to your template library.                                                  |
| Email theme                     | Created as an **unpublished draft**. No email can adopt it until you publish it. |
| Form                            | Created **unpublished**. It isn't live on any page yet.                          |
| Workflow                        | Created **inactive**. It doesn't run until you activate it.                      |

Because nothing goes live, creating an email, form, or workflow doesn't pause for a preview — the draft *is* the preview, and you open it in that asset's normal editor to review before you publish, send, or activate. Other creates (contacts, audiences, campaigns, folders) ask for [approval](/product-docs/conversion-ai/approvals) first.

<Note>
  Workflows are **create-only**. There's no edit flow for an existing workflow — to change one, Conversion AI creates a new workflow you can switch to.
</Note>

## Editing existing assets

When you ask Conversion AI to change an asset that **already exists** — an email, form, audience, or campaign — it doesn't edit it on the spot. Each change is a **proposal**, collected into a pending **edit list** for that turn.

* **Nothing changes while Conversion AI works.** Reads keep showing the asset's current, pre-edit state. An edit that seems to "not take effect" yet is pending by design.
* **You review at the end of the turn.** When the turn ends, all of the edits to each asset are gathered and merged, and you approve or reject them **per asset**.
* **Only approved edits apply.** Rejecting an asset's edits drops them; nothing is written.
* **Several edits to the same asset are merged** (latest value per field wins), so you review one combined change per asset rather than a stack.

What can be edited this way:

| Asset                                   | What an edit can change                                                                                                               |
| --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| Email (blast, workflow email, template) | Name, body, subject, preview text, sender, topic; for blasts, the recipient filter and scheduled send time (the blast stays a draft). |
| Email theme                             | Name and the theme design (colors, fonts, buttons, section palettes). The review includes a preview of the proposed design.           |
| Form                                    | Name and design (fields, layout, theme, settings).                                                                                    |
| Audience                                | Name, type, dynamic filter; for static audiences, which contacts are in it.                                                           |
| Campaign                                | Name, description, members, member statuses, and token values.                                                                        |

<Note>
  **Renaming is just an edit.** To rename an existing email, form, audience, or campaign, Conversion AI sets the new name through the same edit flow, reviewed and applied with the rest of that asset's changes. (Workflows and folders are renamed directly instead, which asks for [approval](/product-docs/conversion-ai/approvals).)
</Note>

## What applying does

Approving an asset's edits applies them, but never goes live on its own:

| Edit                 | What applying does                                                                     |
| -------------------- | -------------------------------------------------------------------------------------- |
| Email or form        | Writes to the asset's **draft**. The change isn't live until you publish the draft.    |
| Email theme          | Writes to the theme's **working draft**. No email changes until you publish the theme. |
| Audience or campaign | Updates the asset directly (filter, membership, name, and so on).                      |

There's always a manual publish, send, or activate step you control. See [Approvals](/product-docs/conversion-ai/approvals) for how the review prompt works.

## Multi-asset builds

A single request can imply several assets at once — "set up a welcome series" might mean three new workflow emails plus a workflow. Conversion AI creates the new assets and proposes any edits together, so you can review the full set in one turn.