--- title: Enabling Push Notifications for Mobile Application slug: kronpam-reference-guide-legacy-ui-3-4-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 Retrieval** retrieval requests can also be sent as push notifications to the Kron PAM mobile application. The users will need to 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. Open the **Trigger List** tab. 3. Select **SendPushMessageJob** 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 **Save**. ::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/ZVUKXcDYdEhjAdhcvhPIb_image.png" size="74" width="980" height="399" caption="SendPushMessageJob” parameters" position="center" showCaption="true"} 1. Navigate to **Administration** > **System Config Man**. 2. Set the **mobile.tomcat.url** parameter as **http\://\/mobile-api/rest** 3. Set the **max.push.count.to.send.in.one.time** parameter as **100** and click **Save**. 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** | **Description** | **Parameter Value Examples** | | ---------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------- | | **aioc.push.notification.message.title.template.connection.approval** | The title of the message to be sent to the approver for a connection approval | Kron | | **aioc.push.notification.message.title.template.connection.expire** | The title of the expire message to be sent to the approver after a connection approval workflow step expires. | Text | | **aioc.push.notification.message.title.template.connection.expire.request.owner** | The title of the expire message to be sent to the request owner after a connection approval workflow step expires. | Text | | **aioc.push.notification.message.body.template.connection.approval** | The body of the message to be sent to the approver for a connection approval | You have pending approval for connecting device ${deviceName}. Requested by: ${username}, with reason: ${reason} | | **aioc.push.notification.message.body.template.connection.expire** | The body of the expire message to be sent to the approver after a connection approval workflow step expires. | Text | | **aioc.push.notification.message.body.template.connection.expire.request.owner** | The body of the expire message to be sent to the request owner after a connection approval workflow step expires. | Text | | **aioc.push.notification.message.title.template.command.approval** | The title of the message to be sent to the approver for a command approval | Kron | | **aioc.push.notification.message.title.template.command.expire** | The title of the expire message to be sent to the approver after a command approval workflow step expires. | Text | | **aioc.push.notification.message.title.template.command.expire.request.owner** | The title of the expire message to be sent to the request owner after a command approval workflow step expires. | Text | | **aioc.push.notification.message.body.template.command.approval** | The body of the message to be sent to the approver for a command approval | You have pending approval for running a command device ${deviceName}. Requested by: ${username}, with reason: ${reason} | | **aioc.push.notification.message.body.template.command.expire** | The body of the expire message to be sent to the approver after a command approval workflow step expires. | Text | | **aioc.push.notification.message.body.template.command.expire.request.owner** | The body of the expire message to be sent to the request owner after a command approval workflow step expires. | Text | | **aioc.push.notification.message.title.template.sapm.approval** | The title of the message to be sent to the approver for SAPM approval | Text | | **aioc.push.notification.message.body.template.sapm.approval** | The body of the message to be sent to the approver for SAPM approval | Text | | **aioc.push.notification.message.body.template.sapm.approval.static** | The body of the message to be sent to the approver for Static SAPM account approval | You have pending approval for Static SAPM account name:${sapmUsername}. Requested by:${username} | | **aioc.push.notification.message.title.template.sapm.second.level.approval** | The title of the message to be sent to the approver for SAPM second level approval | Text | | **aioc.push.notification.message.body.template.sapm.second.level.approval** | The body of the message to be sent to the approver for SAPM second level approval | Text | | **aioc.push.notification.message.body.template.sapm.second.level.approval.static** | The body of the message to be sent to the approver for Static SAPM account second level approval | You have pending second level approval for Static SAPM account name:${sapmUsername}. Requested by:${username} |