> 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/deleteemailservices.md).

# DeleteEmailServices

The **DeleteEmailServices** template allows you to remove specific fields from existing email service configurations in Salesforce.

## Steps to Create the DeleteEmailServices Template

1. Log in to your AutoRABIT account.
2. Navigate to the **Env. Pro.** module.
3. Click **Create New Template**.
4. Open the **Create Unsupported Metadata Template** tab.
5. Enter a **template name** and a **short description**.
6. Select the **DeleteEmailServices** checkbox under **Manage Email Services**.
7. Click **Add**.
8. On the next screen, a **Test Case Name** and **Fields To Delete** are auto-populated. To add custom test data, click **Add**.
9. To change field names for auto-generated or custom test cases:
   * Click the ![Edit Field Icon](/files/0LaBs9muP7HpepnKiaxX) icon.
   * Enter the new field name in the provided text box.
   * To add multiple fields, click the **+** symbol and repeat the above steps.
   * Click **OK** once done.
   * Click **Save** to finalize the configuration for this test case.
10. Click **Save** again to store the template.
11. After successful creation, you will be redirected to the **Environment Provisioning History** screen.
12. Click **Run** to apply the template to your destination org.
13. Select your **destination org** from the dropdown list and provide **email address(es)** for notification purposes.
14. In the **Post Deployment Steps**, select the test cases recently created.
15. For a comprehensive summary of the executed operation, refer to the **View History** page.


---

# 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://knowledgebase.autorabit.com/product-guides/arm/arm-features/environment-provisioning/unsupported-metadata-templates/manage-email-services/deleteemailservices.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.