> For the complete documentation index, see [llms.txt](https://docs.c360.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.c360.org/registration/registration-settings/notifications.md).

# Notifications

There are four notifications configured to be sent when specific events happen within the parent portal. You can configure each one to use a default or customized template.

* Parent: Registration Welcome
* Parent: Registration Complete
* Staff: Parent Registration Complete
* Staff: Participant Enrollment

Parent notifications are sent to the email on file for the parent. Staff notifications can be sent to one or more email addresses, separated by a semicolon. e.g. `email1@gmail.com; email2@gmail.com`.

If you're new to email templates, check out the [docs on creating and managing templates](/locations-files-and-email-templates/email-templates-and-messages/email-templates.md).

### Using Default Templates

To help you get started, we created four email templates that you can use out of the box. You can find these four templates in the `SystemEmails/ParentPortalNotifications` folder for reference.

While these work great out of the box, you should consider changing the default From Address as well as the Reply-to Address on these templates.

<figure><img src="/files/bIT5mFh68mxsD7ywHaI6" alt=""><figcaption></figcaption></figure>

For convenience, these templates are named the same as the field name, in the Parent Portal settings. These are not set by default, so you'll need to select them.

<figure><img src="/files/XzmhppMLNk24skTDp0dd" alt=""><figcaption></figcaption></figure>

### Custom Templates & Merge Fields

If you would like to customize the template used for any notification, the following merge fields are available for use. Please note not every template has access to the same data.&#x20;

<table data-full-width="true"><thead><tr><th>Merge Field</th><th>Default Value</th><th>Example</th></tr></thead><tbody><tr><td><code>parentFirstName</code></td><td>Parent</td><td>Sally</td></tr><tr><td><code>parentLastName</code></td><td></td><td>Smith</td></tr><tr><td><code>parentFullName</code></td><td><code>parentFirstName + parentLastName</code></td><td>Sally Smith</td></tr><tr><td><code>parentPhoneNumber</code></td><td></td><td>1 555-555-5555</td></tr><tr><td><code>participantsList</code></td><td></td><td>Susan Smith (#short-id)</td></tr><tr><td><code>newEnrollmentList</code></td><td></td><td>- Susan Smith (#short-id)<br>-- Summer 23' Enrollment (waitlisted)</td></tr></tbody></table>

If you're new to merge fields, [take a look at the docs](/locations-files-and-email-templates/email-templates-and-messages/email-templates.md#merge-field-format) and the default templates.

#### Example

```
Hey team,

The following participants have just been enrolled via the parent portal!

Parent: ${parentFullName!''}

Enrollments: ${newEnrollmentList!''}

${o_orgName!''}
```

Result

```
Hey team,

The following participants have just been enrolled via the parent portal!

Parent: Sally Smith

Enrollments:

- Emelia Smith (#1018514577)
-- After School Gymnastics (waitlisted)

- Raffael Smith (#1397000694)
-- 2023 Summer Enrollment

My Organization
```

#### Available Fields

As mentioned, not every merge field is available in every notification. Here are the fields you can use in each template.

{% hint style="info" %}
All other standard fields, e.g. `${o_orgName!''}` are always available by default
{% endhint %}

* Parent: Registration Welcome

  * `parentFirstName`
  * `parentLastName`
  * `parentFullName`
  * `parentPhoneNumber`

* Parent: Registration Complete

  * `parentFirstName`
  * `parentLastName`
  * `parentFullName`
  * `parentPhoneNumber`

* Staff: Parent Registration Complete

  * `parentFirstName`
  * `parentLastName`
  * `parentFullName`
  * `parentPhoneNumber`
  * `participantsList`

* Staff: Participant Enrollment
  * `parentFirstName`
  * `parentLastName`
  * `parentFullName`
  * `parentPhoneNumber`
  * `newEnrollmentList`


---

# 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:

```
GET https://docs.c360.org/registration/registration-settings/notifications.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.