---
title: "Push settings"
slug: "web-push-prompt-settings"
updated: 2026-06-09T09:55:40Z
published: 2026-06-09T09:55:40Z
canonical: "docs.xtremepush.com/web-push-prompt-settings"
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.xtremepush.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Push settings

Configure the push notification settings for all of your integrated apps and websites

Once you have integrated your applications and websites by adding the Xtremepush SDKs to your [Android app](/documentation/docs/android-integration), [iOS app](/documentation/docs/ios-integration), and [website](/documentation/docs/website-integration), you can use *Push settings* to update the integration credentials and control how and when your users get asked to opt-in for push notifications.

To access push settings for your connected apps & sites navigate to **Settings > Apps & sites >** click on the matching app or website **> Push Settings**.

## iOS push

Upload your *Production* and *Sandbox* push notification certificates [retrieved from the Apple developer portal](/documentation/docs/ios-push-notifications#section-get-apple-certificates). If your current push notification certificate has expired you can upload the new certificates here, and the **Push** channel for this iOS app will show a red indicator.

![1820](https://cdn.document360.io/b056e88b-f6c1-4bd2-b5b8-08e9336a17c9/Images/Documentation/92db339-Screenshot_2022-05-10_at_12.10.12(1).png)

The red indicator close to the iOS app shows that the certificates have expired.

Click **Update** once you have uploaded the new certificates. The indicator should change to green if the new certificate is validated.

## Android push

Enter your *Firebase Sender ID* and *Server Key*, they can be [retrieved from the Google Firebase console](/documentation/docs/android-push-notifications#section-get-configuration-values).

Click **Save**.

> [!CAUTION]
> Any opted-in users are opted-in against your Sender ID on Firebase. If you change the Sender ID of an existing integration you will lose your current subscribers.

## Web push

Push notifications can be toggled using the sliders for individual browsers. For full implementation instructions, see the web channel guides for [Push notifications for Chrome/Opera and Firefox](/documentation/docs/web-push-notifications) and [Apple push notifications for Safari](/documentation/docs/apple-push-notifications-for-safari).

## Web push permissions prompt settings

Toggle the **Auto prompt permission dialog** to automatically trigger the push notification opt-in prompt for all users on your website.

**Prompt at** is used to delay when the user is prompted for push permissions. For example, if you set the **Prompt at** to *3 page views*, the user will be asked if they want to accept notifications on their 3rd page view on your website.

The **If no repeat after** setting only applies to *Chrome/Opera and Firefox Push Notifications* when a subscribe window is selected for self-hosted domains. If the user selects **No** at the first dialog the subscribe window will not appear. Changing the **If no repeat after** setting allows you to ask again after a number of page views on Chrome, Opera or Firefox.

You can also optionally set URLs to redirect the user based on their interaction with the permission prompt and customise the message used for the value exchange using the **Description** field.

> [!NOTE]
> Custom prompts
> 
> It's possible to override the *Auto Prompt* for key pages, for example, to suppress a prompt during a store checkout process. This is covered in the [integration guide for customising the web notification prompt](/documentation/docs/web-custom-push-subscribe-prompt).
> 
> We recommend deploying a two-step prompt with a value exchange for best results. Review our dedicated [guide](/documentation/docs/web-two-step-prompt) on this topic for detailed instructions.