> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/arm/arm-features/environment-provisioning/unsupported-metadata-templates/manage-email-services/newemailservices.md).

# NewEmailServices

The **NewEmailServices** template allows users to configure new Email Service records in a Salesforce org via AutoRABIT's Environment Provisioning.

## Steps to Create the NewEmailServices Template

1. Log in to your AutoRABIT account.
2. Go to the **Env. Pro.** module.
3. Click on **Create New Template**.
4. Navigate to the **Create** [**Unsupported Metadata Template**](/product-guides/arm/arm-features/environment-provisioning/unsupported-metadata-templates.md) tab.
5. Enter a **template name** and a **short description**.
6. Select the **NewEmailServices** checkbox under **Manage Email Services**.
7. Click **Add**.
8. On the next screen, a **Test Case Name** appears by default.

   * Click the **Add** button to provide custom test data.
   * Fill in the required fields with appropriate values.
   * Click **Save**.

   ![New Email Services Test Case](https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FmGHFovF9txu6RMjp53EZ%2Fimage.png?alt=media\&token=35e8e772-6a62-4c4b-9ebe-a6e24936493d)
9. Click **Save** again to save the template.
10. After saving, you'll be redirected to the **Environment Provisioning History** screen.
11. Click **Run** to execute the template on your selected destination org.
12. Choose your **destination org** from the dropdown and enter the **email address(es)** for deployment notifications.
13. In the **Post Deployment Steps**, select the test cases you recently created.
14. Review the **View History** page for a comprehensive summary of the deployment operation.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledgebase.autorabit.com/product-guides/arm/arm-features/environment-provisioning/unsupported-metadata-templates/manage-email-services/newemailservices.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.