> 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/report-dashboards-create-manage-folders/deletefolder.md).

# Delete Folder

The **DeleteFolder** template allows you to delete report or dashboard folders in Salesforce using AutoRABIT’s Environment Provisioning module.

## Steps to Create the DeleteFolder Template

1. Log in to your AutoRABIT account.
2. Navigate to the **Env. Pro.** module.
3. Click on **Create New Template**.
4. Select the **Create Unsupported Metadata Template** tab.
5. Enter a **name** and a **short description** for the template.
6. Check the **DeleteFolder** option under **Report Dashboards Create Manage Folders**.
7. Click **Add**.
8. On the next screen:
   * A **Test Case Name** is auto-generated by default.
   * Click **Add** to create custom test data.
   * In the **Delete Folder Name** field, enter the name of the folder to be deleted.
   * Click **Save** to store the data.
9. Click **Save** again to finalize the template.
10. Upon successful creation, you'll be redirected to the **Environment Provisioning History** screen.
11. Click the **Run** button to deploy the template to the destination org.
12. Select the **destination org** from the dropdown and specify **email address(es)** to receive deployment notifications.
13. Under **Post Deployment Steps**, select the test cases you recently created.
14. Visit the **View History** page for a comprehensive summary of the deployment.


---

# 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/report-dashboards-create-manage-folders/deletefolder.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.