> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/trulyp/vizzy-studio/writeback.md).

# Add writeback to a visualization

A Studio visualization can also collect data: a form or an editable table that writes back to your database, just like WriteBackExtreme. Vizzy builds the form; you connect it to a writeback schema that stores the submissions.

### Build a writeback visualization

Ask for a form or editable table in your prompt, or start from the **Writeback table with inline editing** prompt idea. When Vizzy recognises writeback, the workspace shows a **Writeback** card:

* **Writeback not connected**: "Connect this form to a writeback schema so submissions have somewhere to go." Click **Add writeback**.
* **Writeback connected**: "Submissions are written to *table*", with the **Table**, **Connection**, **Primary key** and **Fields**. Click **Review writeback** to see the setup.
* **Connected schema missing**: the schema was deleted. Click **Review writeback** to connect a new one.

You can also ask Vizzy to set up writeback; it offers buttons such as **Set Up Writeback**.

### Connect a writeback schema

**Add writeback** opens **Create Writeback Instance**:

1. Choose the **Connection** where the data should be stored.
2. Check the **Schema label** and **Table name** (filled in from the visualization's name).
3. Under the field checklist, select the form fields to store, or use **Select all** / **Clear all**.
4. Click **Create And Connect**.

Trulyp creates a [Data Correction schema](/trulyp/writebackextreme/schemas/what-type-of-schema/correct-or-update-existing-data.md) with an `id` primary key and the selected fields, creates its table in your database, connects it to the visualization, and rebuilds it ("Writeback schema created and connected.").

You need the **Schema manager** role to do this. The new schema shows up in **WriteBackExtreme** › **Schemas**, where you can set its [permissions](/trulyp/writebackextreme/schemas/schema-permissions.md) and [row-level security](/trulyp/writebackextreme/schemas/row-level-security.md).

{% hint style="info" %}
In Tableau, a writeback visualization asks people to **Sign in with Tableau** before they can submit data, so Trulyp knows who wrote what.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.infotopics.com/trulyp/vizzy-studio/writeback.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.