> 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/web-to-lead/edit-web-lead.md).

# Edit Web Lead

The **EditWebLead** template allows you to configure or update Web-to-Lead settings in your Salesforce org via AutoRABIT's Environment Provisioning module.

## Steps to Create the EditWebLead 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 **EditWebLead** checkbox under **Web to Lead**.
7. Click **Add**.
8. On the next screen:

   * A **Test Case Name** will be displayed by default.
   * Click **Add** to input custom test data.
   * Fill in the following fields:
     * **Enabled:** Enable Web-to-Lead functionality for your organization.
     * **Default Lead Creator:** Specify the username that will be assigned as the creator of online leads.
     * **Default Response Template:** Provide a default email template to be used if no auto-response rule is matched.
   * Click **Save** to save the configuration.

   ![Edit Web Lead Settings](https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FLQrgU5wZV6exiCMCsn8S%2Fimage.png?alt=media\&token=051b2c11-d637-4f4d-b05c-a040590089c8)
9. Click **Save** again to finalize the template.
10. You will be redirected to the **Environment Provisioning History** screen.
11. Click **Run** to execute the template on your destination org.
12. Select your **destination org** and enter the **email address(es)** to receive run notifications.
13. In the **Post Deployment Steps**, select the test cases you created.
14. Visit the **View History** page to review a detailed summary of the 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/web-to-lead/edit-web-lead.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.