> 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/mobile-administration/mobiledashboardsettings.md).

# Mobile Dashboard Settings

The **MobileDashboardSettings** template enables the configuration of mobile dashboard accessibility settings within Salesforce, specifically for the iPad app, via AutoRABIT’s Environment Provisioning.

## Steps to Create the MobileDashboardSettings Template

1. Log in to your AutoRABIT account.
2. Click on the **Env. Pro.** module.
3. Click **Create New Template**.
4. Navigate to the **Create Unsupported Metadata Template** tab.
5. Provide a **template name** and a **short description**.
6. Check the **MobileDashboardSettings** checkbox under **Mobile Administration**.
7. Click **Add**.
8. On the next screen:
   * A **Test Case Name** is generated by default.
   * Click **Add** to define custom test data and provide a name.
9. Select the **Enable Mobile Dashboard iPad App** checkbox to activate the setting, then click **Save** to store the test configuration.
10. Click **Save** again to save the template.
11. Upon successful template creation, you'll be redirected to the **Environment Provisioning History** screen.
12. Click **Run** to execute the template against the selected destination org.
13. Choose your **destination org** from the dropdown menu and provide **email address(es)** for notification.
14. In the **Post Deployment Steps**, select the test cases you recently created.
15. Visit the **View History** page to view a detailed summary of the provisioning 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/mobile-administration/mobiledashboardsettings.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.