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

# Edit Lead Settings

The **EditLead** template allows users to modify lead ownership and conversion settings in Salesforce using AutoRABIT.

## Steps to Create the Edit Lead Template

1. Log in to your AutoRABIT account.
2. Navigate to the **Env. Pro.** module.
3. Click **Create New Template**.
4. Go to the **Create Unsupported Metadata Template** tab.
5. Enter a **template name** and a **short description**.
6. Select the **EditLead** checkbox under **Lead Settings**.
7. Click **Add**.
8. On the next screen:
   * A **Test Case Name** is auto-generated.
   * Click **Add** to insert custom test data.
   * Fill in the following fields:

     * **Lead Type:** Specify a queue or user to assign the lead if assignment rules fail.
     * **Lead Owner:** Enter the designated lead owner.
     * **Lead Conversion Setting:** Click the configuration icon ![icon](https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FpqfCvWgQvj5HcYJyjFMr%2Fimage.png?alt=media\&token=05ff23b2-bcfb-48ca-9a5d-41dd7e94700b) to open the settings panel and configure:
       * **Require Validation for Converted Leads:** Enforces field-level validations, workflow actions, and triggers on conversion.
       * **Preserve Lead Status:** Retains the lead's original status instead of using the new owner’s default.
       * **Enable Conversions for Salesforce Mobile:** Allows lead conversion from the Salesforce mobile app.

     ![Lead Conversion Settings](https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FfQC4OkWyVcIkjE5xIdOI%2Fimage.png?alt=media\&token=d2092bed-2c82-43c1-abc6-59bdd505a995)
   * Activate the settings using the **Active** checkbox.
   * Click **Save** to finalize the data entry.
9. Click **Save** again to create the template.
10. You’ll be redirected to the **Environment Provisioning History** screen.
11. Click **Run** to execute the template on your destination org.
12. Choose your **destination org** and enter **email address(es)** for execution notifications.
13. In the **Post Deployment Steps**, select the test cases you created.
14. Visit the **View History** page for a comprehensive execution summary.


---

# 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/editlead.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.