> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dapta-forms/account/notifications.md). # Notification emails (account templates) Edit the two account-wide submission emails in Dapta Forms: the new submission notice and the respondent confirmation. Turn each one on or off, rewrite the subject and body, insert variables, check th Dapta Forms sends two emails when a form is submitted: one to you, and one to the person who answered. Both are written once for the whole workspace and every form uses them, unless that form overrides them from its **Connect** tab. This page is where you edit the workspace-wide copy. > **⚠️ Note:** Only admins and owners of the workspace can edit these templates. Members see the notice **Only admins and owners of this workspace can edit its notification emails.** *** **Step 1:** Click your name at the bottom of the left menu to open the account menu, then choose **Notifications** under **Account settings**. You land on **Account settings** with the **Notifications** tab selected.

The Notifications tab of Account settings showing the New submission notice card with its Send this email switch, Subject and Body — Notifications sits next to Workspaces, Brand kit and Public page. The **Managing** chip above the card names the workspace these templates belong to.

The page holds two cards, and that is the complete list of emails Dapta Forms sends about submissions: | Email | When it is sent | | --------------------------- | ------------------------------------------------------------- | | **New submission notice** | Sent to you when someone submits a form. | | **Respondent confirmation** | Sent to the respondent to confirm you received their answers. | *** **Step 2:** Use the **Send this email** switch to decide whether the email goes out at all. The helper text reads **Turn off to stop sending this email entirely.** Turning it off stops that email for every form in the workspace. *** **Step 3:** Rewrite the **Subject** and the **Body**. Both are plain text boxes, and both start out holding the default copy so you can edit rather than write from scratch. The stock copy looks like this: | Email | Subject | Body | | --------------------------- | ------------------------------------- | --------------------------------------------------------------------------------------------------------------- | | **New submission notice** | `New submission: {{formName}}` | `You have a new submission on "{{formName}}".` then `From:`, `Score:`, `Outcome:` and `View submissions:` lines | | **Respondent confirmation** | `We got your responses: {{formName}}` | `Thanks: we've recorded your responses to "{{formName}}."` then a `View or edit:` line | *** **Step 4:** Add a variable anywhere in the subject or the body. Under **Available variables** the helper text reads **Click a variable to insert it. Each is replaced with the real value when the email is sent.** Click a chip and it drops into the field you were last typing in. **Preview** below shows the finished email with sample values, so you can see the result before you save.

The Available variables chips and the Preview box of the New submission notice, with the Save changes button — **Available variables** inserts a placeholder, **Preview** renders the email with sample values.

| Variable | What it becomes | | --------------------- | ---------------- | | `{{formName}}` | Form name | | `{{respondentEmail}}` | Respondent email | | `{{score}}` | Score | | `{{outcomeLabel}}` | Outcome | | `{{formLink}}` | Form link | > **💡 Tip:** Anything that is not one of these five variables is left exactly as you typed it, braces included. If a variable comes out empty in a real email, the form simply had nothing to put there (no score, no outcome, no email question). *** **Step 5:** Click **Save changes**. The chip in the top right of the card switches from **Using default** to **Customized**, which is how you tell at a glance whether an email still carries the stock copy.

The New submission notice card with a rewritten subject, the Customized chip and the Reset to default button — Once you save your own copy the chip reads **Customized** and **Reset to default** becomes the way back.

*** **Step 6:** To undo your edits, click **Reset to default**. A confirmation asks **Reset this email's subject and body to the default copy?** Confirm with **Reset to default** and the card returns to the stock subject and body, and to the **Using default** chip. The **Send this email** switch is not touched by a reset. *** ## Which copy an email actually uses Each field is resolved on its own, in this order: 1. The form's own override, set on that form's **Connect** tab. 2. The account template on this page. 3. The stock copy that ships with Dapta Forms. So a form can override just the subject and keep your account body, and a form with no override at all follows whatever you write here. The stock copy exists in English and in Spanish, and Dapta Forms picks the language for you. The moment you save your own subject or body, that exact text is sent instead, in whichever language you wrote it. > **⚠️ Note:** The address the emails are sent from is set by the deployment. It is not editable per account or per form. *** ## Overriding these emails for one form Open a form, go to its **Connect** tab and scroll to **Emails**. Each card there shows **Using the account template** or **Custom for this form**, with a muted **Subject:** preview underneath. * **Customize for this form** copies the current template into that form and opens the same editor you used here. * **Use account template** removes the form's copy. It asks **Remove this form's custom copy and go back to the account template?** first. The footnote on that section points back to this page: the account-wide templates live in **Settings → Notifications**. Full details are in [Submission emails](/dapta-forms/connect/emails.md). *** ## What's next * [Submission emails](/dapta-forms/connect/emails.md): the per-form overrides and the email delivery history. * [Brand kit (workspace-wide)](/dapta-forms/design/brand-kit.md): the other setting that applies to every form at once. * [Members & roles](/dapta-forms/account/members-and-roles.md): who is allowed to edit these templates. * [Public page & identity](/dapta-forms/account/public-page-and-identity.md): the page at your handle that lists your published forms. --- # 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://docs.dapta.ai/dapta-forms/account/notifications.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.