> 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/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](https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FMAQ8DE6PproJHYnjJwH2%2Fimage.png?alt=media\&token=598bfee3-5329-46e6-88ca-be9ea93ee8c0)
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 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/mobilenotifications.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.