> For the complete documentation index, see [llms.txt](https://orbit-b2b.gitbook.io/orbit-b2b-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://orbit-b2b.gitbook.io/orbit-b2b-docs/email-notifications/templates.md).

# Customize email templates

## Open the template editor

1. Go to **Registration → Email Settings**
2. In the left sidebar, click a template name:
   * **Registration Confirm** — verify-email step before review
   * **New Submission** (sent to you)
   * **Application Approved** — for Individual and Join-company approvals
   * **Company Registration Approved** — for new-company approvals; body includes the new company's invite link so the contact can share it with their staff
   * **Application Rejected** — sent on reject with an edit link
   * **Auto-Approved** — sent when auto-approve fires
   * **Company Invite** — sent from a Company's Registration tab when you invite contacts manually

***

## What you can edit

| Field       | Description                                                      |
| ----------- | ---------------------------------------------------------------- |
| **Enabled** | Toggle to enable or disable this email                           |
| **Subject** | Email subject line — supports shortcodes                         |
| **Body**    | Rich-text email content — supports shortcodes, formatting, links |

***

## Formatting options

The body editor supports:

* Headings (H2)
* Bold, italic
* Bulleted and numbered lists
* Blockquotes (shown as a red alert box in the email)
* Links — a standalone link on its own line is automatically styled as a **button**

***

## Reset to default

If you've edited a template and want to start fresh:

1. Open the template
2. Click **Reset to default** in the right sidebar
3. Confirm — the default content is restored

***

## Preview

Click **Preview email** to open a preview of the full email in a new tab, with all styles applied as they would appear in an email client.

***

## Tips

* Keep the **New Submission** email short — it's just a notification to you.
* In the **Rejection** email, include `{{edit_link}}` so customers can resubmit their application.
* In **Approved** / **Auto-Approved** emails, use `{{group_name}}` to confirm which tier the customer was assigned to.
* In **Company Registration Approved**, include `{{company_register_link}}` so the contact can share it with their team for self-registration.

***

## Translations

Each template has its own per-locale subject + body. Switch the locale dropdown at the top of the editor to author a translation for any published storefront language. Fields left empty fall back to the primary locale.

Out-of-the-box translations ship for **Vietnamese, French, German, Spanish, and Japanese** on the `company_registration_approved` template — pick a locale, click **Restore defaults** to load them, then edit if needed. New shops get all locales pre-seeded automatically.


---

# 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://orbit-b2b.gitbook.io/orbit-b2b-docs/email-notifications/templates.md?ask=<question>&goal=<endgoal>
```

`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.