# Email templates

We use [PUG ](https://pugjs.org/api/getting-started.html)template engine to build the emails that will be sent to the user in the authentication process copy the ready to use templates to your app you can always customize the emails in the future\
\
1- **Create new folder** - create "email-templates" folder inside src folder

2- **Open** node\_modules\feathers-mongoose-casl\lib\src\services\authmanagement\email-templates

3- **Copy** the account folder to your new email-templates folder

<div align="left"><img src="https://1499183940-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LY13uPlo20E7hNPj1d2%2F-LY1JHpStjHaXRbHFgc7%2F-LY1Vv4-mBm-olZ-e1QN%2FCapture.JPG?alt=media&#x26;token=0ee198e8-ba35-4e90-b547-4416b34b7f19" alt=""></div>

3 - **Git commit**

```
git add .
git commit -m "create email-templates folder to verified user email"
```


---

# Agent Instructions: 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://feathersjs-mongoose.gitbook.io/feathers-mongoose-casl/docs/start-new-project-1/email-templates.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.