---
title: Enabling Push Notifications for Mobile Application
slug: kronpam-reference-guide-3-6-0/enabling-push-notifications-for-mobile-application
description: Learn how to enable push notifications for the Kron PAM mobile application with this comprehensive guide. Get step-by-step instructions on configuring necessary parameters in the Administration GUI and customizing notification messages. Log in to the mobi
docTags: 
createdAt: 2022-07-22T10:21:52.000Z
---

The email notifications for **Command**, **Connection**, and **SAPM approval requests** can also be sent as push notifications to the Kron PAM mobile application. The users must log in to Kron PAM at least once via their mobile application to receive these notifications.

To enable push notifications for mobile applications in the Administration GUI:

1. Navigate to **Administration** > **Jobs Scheduler**
2. Click the** +Add** button.
3. Select **SCPolicyNotifierJob **as the Job
4.  Fill in the fields, **Trigger Name** and **Cron Expression**.
5. On the **Active** field select **Enabled** to enable the job and click **Add Trigger**.
6. Select **SendPushMessageJob** as the Job
7. Fill in the fields, **Trigger Name** and **Cron Expression**.
8. On the **Active** field select **Enabled** to enable the job and click **Add Trigger**.

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/nuwDlsCh9FmHS0S-26ei7_image.png" size="70" width="744" height="609" position="center" caption="SendPushMessageJob parameters" showCaption="true"}

- Navigate to **Administration > System Config Man.**
- Set the** mobile.tomcat.url **parameter as **https\://KronPAM\_IPAddress:9443/mobile-api/rest**
- Set the** max.push.count.to.send.in.one.time” **parameter as **100** and click **Save**.
- When mobile-api server (e.g., 10.20.42.42) is different from the KronPAM server (e.g., 10.20.42.41), it is necessary to add the "internal.bind.host" parameter to conf/application.properties file of KronPAM server as shown below:

After these settings are in place, the users will start getting mobile notifications for the cases stated above. For the configurations of each case, please refer to the related sections.

| **Parameter Name**                                                                 |
| ---------------------------------------------------------------------------------- |
| **aioc.push.notification.message.title.template.connection.approval**              |
| **aioc.push.notification.message.title.template.connection.expire**                |
| **aioc.push.notification.message.title.template.connection.expire.request.owner**  |
| **aioc.push.notification.message.body.template.connection.approval**               |
| **aioc.push.notification.message.body.template.connection.expire**                 |
| **aioc.push.notification.message.body.template.connection.expire.request.owner**   |
| **aioc.push.notification.message.title.template.command.approval**                 |
| **aioc.push.notification.message.title.template.command.expire**                   |
| **aioc.push.notification.message.title.template.command.expire.request.owner**     |
| **aioc.push.notification.message.body.template.command.approval**                  |
| **aioc.push.notification.message.body.template.command.expire**                    |
| **aioc.push.notification.message.body.template.command.expire.request.owner**      |
| **aioc.push.notification.message.title.template.sapm.approval**                    |
| **aioc.push.notification.message.body.template.sapm.approval**                     |
| **aioc.push.notification.message.body.template.sapm.approval.static**              |
| **aioc.push.notification.message.title.template.sapm.second.level.approval**       |
| **aioc.push.notification.message.body.template.sapm.second.level.approval**        |
| **aioc.push.notification.message.body.template.sapm.second.level.approval.static** |