> 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-1/arm-features/environment-provisioning/unsupported-metadata-templates/create-organization-wide-email-footers/editemailfooters.md).

# Edit Email Footers

The **EditEmailFooters** template is used to modify existing organization-wide email footers within your Salesforce environment.

## Steps to Create the EditEmailFooters Template

1. Log in to your AutoRABIT account.
2. Navigate to the **Env. Pro.** module.
3. Click on **Create New Template**.
4. Open the [**Create Unsupported Metadata Template**](https://knowledgebase.autorabit.com/docs/unsupported-metadata-templates) tab.
5. Provide a **template name** and a **short description**.
6. Select the **EditEmailFooters** checkbox under **Create Organization-Wide Email Footers**.
7. Click **Add**.
8. On the next screen:
   * A **Test Case Name** will appear by default.
   * Click **Add** to input custom test data.
   * Fill in the following fields:
     * **Edit Footer:** Enter the footer details you wish to edit.
     * **Name:** Specify the name of the footer.
     * **Active for Single Email:** Enable this option to activate the footer for single emails.
     * **Active for Mass Email:** Enable this option to activate the footer for mass emails.
     * **Email Encoding:** Provide the desired email encoding format.
     * **Text:** Add any additional footer content or comments.
   * Click **Save** once complete.
9. Click **Save** again to finalize the template.
10. Upon successful creation, you will be redirected to the [**Environment Provisioning History**](https://knowledgebase.autorabit.com/docs/environment-provisioning) screen.
11. Click **Run** to execute the template on your destination org.
12. Select your **destination org** from the dropdown and provide **email address(es)** for notification.
13. In **Post Deployment Steps**, select the test cases you recently created.
14. For a complete summary of the operation, visit 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 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-1/arm-features/environment-provisioning/unsupported-metadata-templates/create-organization-wide-email-footers/editemailfooters.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.