> For the complete documentation index, see [llms.txt](https://help.tahua.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tahua.io/product-news/2026/readme/add-ability-to-define-content-for-confirmation-instructions.md).

# Add ability to define content for confirmation instructions

## Problem

The confirmation instruction emails sent to new users during registration used fixed templates that organisations could not customise. This was inconsistent with other automated emails (such as invitations) which are already editable, and prevented organisations from adding their own branding, messaging, or role-specific instructions.

## How it works

Organisations can now customise two confirmation-related emails for each user role (Admin, Applicant, Assessor, Verifier):

1. **Confirmation Instructions** -- sent immediately after signup, asking the user to confirm their email address.
2. **Confirmation Reminder** -- sent one day before the confirmation window expires, warning the user to confirm before their account is locked.

### Configuration

Navigate to **Settings > Emails**. The confirmation emails appear under the "Registrations" section for each user type. Click **Edit** to customise the subject line and body content.

### Available personalisations

Emails support the same personalisation variable system as other automated emails. Common variables include:

* `[[confirmation_link]]` -- clickable link to confirm the account
* `[[confirmation_url]]` -- plain URL for pasting into a browser
* `[[time_to_confirm]]` -- human-readable time window (initial email only)
* `[[confirmed_time_ago]]` -- time since the original email was sent (reminder only)
* Recipient name variables specific to each user type (e.g. `[[applicant_first_name]]`, `[[admin_name]]`)

### Defaults

All emails ship with sensible default content. Organisations can restore defaults at any time after customising.


---

# 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.tahua.io/product-news/2026/readme/add-ability-to-define-content-for-confirmation-instructions.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.