> For the complete documentation index, see [llms.txt](https://help.form.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.form.io/form-building/actions/save-submission-actions.md).
# Save Submission Actions
This action dictates what Resource and related Resource fields the form data will save to. Every form or Resource created will carry a Save Submission action. When left unmodified, the action will save the data to itself by default.
Mapping the Save Submission action to other Resources allows a Form to feed a resource database. The most common example is a Registration form. When a user Registers, the submitted data most likely will need to be saved to some sort of User Resource to build a User database collection.
Save Submission action mapped to the User Resource
## Settings
**Save Submission To:** Select which Resource the submission data should map to. When left blank (default), the submission will save to itself.
**Resource Property:** Set a Property to the mapped Resource that will be assigned to.
**Simple Mappings:** When a Resource is selected, the available fields from that Resource will become available for mapping in the Simple Mappings section. Clicking a field will present a Dropdown of fields from the Form the action is attached to where fields from your Form are mapped to fields from the Resource.
**Transform Data:** Use the Transform Data if you are trying to map fields inside complex data structures like EditGrids, Containers, Nested Forms, etc. Available variables are Submission and Data.
## Walkthrough
In this example, we are going to configure a Save Submission action on a Registration form to map submission data to a User Resource. In turn, as the Registration form collects submissions, the Resource will build its database of Users within the project.
To start, **create a Resource** called Users and add the following fields:
Email - Email
Password - Password
Next, create a Form called Registration. **Add the following fields**:
First Name - Textfield
Last Name - Textfield
UserName - Textfield
Email - Email
Password - Password
Click the Action tab for the Registration form and add another **Save Submission action**. Within the Action settings, click the Save Submission To dropdown and select the **User resource**. Next, **map the Email and Password fields** from the form to the Resource fields presented in the Save Submission Action. Save your action.
To test the action, **Use** the Registration form and make a **submission**.
The submission should map to the User Resource, creating a submission record. To verify this, navigate to your User resource and click the **Data tab**. There should be a new submission entry from the Registration form.
{% hint style="info" %}
Encrypted password data will not display when viewing a submission.
{% endhint %}
## Video
{% embed url="" %}
---
# 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://help.form.io/form-building/actions/save-submission-actions.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.