> 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/mobile-salesforce-settings.md).

# Mobile Salesforce Settings

The **MobileSalesforceSettings** template allows the configuration of mobile-specific Salesforce settings via AutoRABIT’s Environment Provisioning.

## Steps to Create the MobileSalesforceSettings Template

1. Log in to your AutoRABIT account.
2. Click on the **Env. Pro.** module.
3. Select **Create New Template**.
4. Go to the **Create Unsupported Metadata Template** tab.
5. Provide a **template name** and a **short description**.
6. Select the **MobileSalesforceSettings** checkbox under **Mobile Administration**.
7. Click **Add**.
8. On the next screen:
   * A **Test Case Name** will appear by default.
   * Click **Add** to create custom test data and assign a name.
9. Check the following settings:

   * **Mobile Browser App Settings**
   * **Device Access Settings**

   Then click **Save** to confirm and store the configuration.

   ![Mobile Salesforce Settings Configuration](/files/mnpGTfjxP6IBG3dIaOou)
10. Click **Save** again to save the template.
11. Once saved, you will be redirected to the **Environment Provisioning History** screen.
12. Click **Run** to execute the template on the selected destination org.
13. Choose your **destination org** from the dropdown and specify **email address(es)** for notifications.
14. In the **Post Deployment Steps**, select the test cases that were just created.
15. Visit the **View History** page for a comprehensive summary of the deployment activity.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledgebase.autorabit.com/product-guides/arm/arm-features/environment-provisioning/unsupported-metadata-templates/mobile-administration/mobile-salesforce-settings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.