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

# Mobile Notifications

The **MobileNotifications** template configures mobile notification preferences for Salesforce via AutoRABIT’s Environment Provisioning.

## Steps to Create the MobileNotifications 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. Select the **MobileNotifications** 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 assign a name.
9. Check the following options to enable them:

   * **Enable in-App Notifications**
   * **Enable Push Notifications**
   * **Enable Full Content**

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

   ![Mobile Notifications Settings](/files/xo28czWyRWsMOKQctQLu)
10. Click **Save** again to save the template.
11. After successful creation, you will be redirected to the **Environment Provisioning History** screen.
12. Click **Run** to execute the template on your destination org.
13. Select the **destination org** from the dropdown and enter the **email address(es)** to receive run notifications.
14. In the **Post Deployment Steps**, choose the test cases you have just created.
15. Refer to the **View History** page for a comprehensive 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 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-1/arm-features/environment-provisioning/unsupported-metadata-templates/mobile-administration/mobilenotifications.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.