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

# Chatflow Reset Control

> Control whether end users can reset a chatflow and clear their answers

The **Chatflow Reset** setting controls whether the reset button is shown to end users in a published chatflow. Resetting clears the user's answers and starts the chatflow over, so when that button appears has direct **compliance implications** — a customer should not be left thinking they can delete their data after a form has already been submitted.

This is a flow-level setting, configured once on the chatflow template, that applies to every published instance of the flow.

***

## Reset modes

Choose one of three modes for the reset button:

| Mode                | Behaviour                                                             |
| ------------------- | --------------------------------------------------------------------- |
| **Off** *(default)* | The reset button is never shown.                                      |
| **On**              | The reset button is always visible while the user is in the chatflow. |
| **On completion**   | The reset button appears only once the chatflow is complete.          |

<Note>
  **Off is the safe default.** The reset button is hidden unless you deliberately enable it. This prevents users from assuming their answers can be cleared after submission, which would otherwise create a compliance gap.
</Note>

***

## Configuring reset

1. Open your flow in the **Flow Builder**.
2. Go to the chatflow **settings**.
3. Set **Chatflow Reset** to **Off**, **On**, or **On completion**.
4. Publish the flow for the change to take effect on the live chatflow.

***

## Choosing a mode

* **Off** — Use for any flow that submits or persists customer data where a post-submission reset would be misleading. This is most regulated, customer-facing flows.
* **On** — Use for demos, testing, or internal tools where letting users restart freely is helpful and there are no data-retention concerns.
* **On completion** — Use when you want users to be able to run the flow again after finishing — for example a repeatable calculator — without exposing a reset mid-flow.

***

## Next Steps

<CardGroup cols={2}>
  <Card title="Flow Builder Basics" icon="hammer" href="/features/flow-builder-basics">
    Learn the fundamentals of building flows
  </Card>

  <Card title="Theme Editor" icon="palette" href="/features/theme-editor">
    Configure other flow-level settings and appearance
  </Card>
</CardGroup>