Goal

Add an Enable Push Notifications button to your app. When a user taps it, the app opens the device’s own notification settings screen for your app, so they can turn notifications on (or back on, if they previously declined). This gives users a clear, one-tap path to opt in instead of hunting through their phone’s Settings app.

It’s about as no-code as a button gets: pick the content type, place it, name it, and publish. There’s nothing else to configure.

Why a separate button?

Here’s the catch with notifications on iOS and Android: a user only gets asked once. Tap “Don’t Allow” the first time, and your app can never show that prompt again — the only way back in is the phone’s own notification settings screen for the app. That’s exactly what this button is for. Tapping it deep-links the user straight to that OS screen, where they can flip notifications back on. It’s the button we recommend pairing with any push-notification setup, and it works especially well alongside an onboarding screen that explains why a user should turn notifications on in the first place.

You’ll recognize the pattern — it’s the same one behind the Enable Location Services button: a simple action button that hands off to the device’s own permission settings.

Before you start

• Where you work. This all happens in the WordPress admin under Mobile App Manager → App Setup — no code, and no App Store / Play Store rebuild. The button ships as app content the moment you publish.
• It’s a content type, not a plugin. “Enable Push Notifications” is one of the built-in content types (button types) that ship with MAM Suite core, so there’s nothing extra to install before it shows up in the content-type list.
• The button has no settings. Unlike a Web URL or a listing screen, this button doesn’t take a content source or any per-button options. When you select it, the settings area will just read “No settings required” — that’s expected, not a glitch.
• What it does and doesn’t do. The button opens the device’s notification settings, full stop. It doesn’t send notifications, and it doesn’t wire up your push-notification provider on its own — that’s configured separately. All this button does is give users a path to opt in.
• A note on naming. UI labels (tab names, button text, section headers) are described here as they appear in a standard install. Yours may word things slightly differently, but the flow is the same.

Steps

1. Open App Setup and choose a placement

1. In the WordPress admin, go to Mobile App Manager → App Setup.
2. Decide where the button should live:
   • On the Home Page tab to put it in the main grid / tab bar.
   • On the Left Menu tab to put it in the slide-out drawer. The left menu is a common home for opt-in and settings actions like this one.
3. If your app uses managed user roles, set the Content for Role dropdown to the role whose app you’re editing first. Buttons are stored per role.

2. Add a button

1. Scroll past your existing buttons to the add-new section at the bottom of the list (the red + with “Click the + to add a button to your app”).
2. Click the +. A new button is created at the bottom of the list with a default name and content type so there’s always something to configure.

3. Choose the “Enable Push Notifications” content type

1. Expand the new button if it isn’t already open.
2. Open the Content Type dropdown inside the button’s options.
3. Select Enable Push Notifications.

Once you select it, the settings area shows “No settings required” — there’s no content source to fill in, because this button already knows what to do: open the device’s notification settings the moment someone taps it.

4. Name the button and set its icon

1. In the button’s header row, type the button name users will see — for example Turn On Notifications, Enable Alerts, or Notification Settings.
2. Click the icon area to pick an image. Choose from the bundled icon sets (Font Awesome, Ionic, the Popular set) or your media library. A bell or alert icon reads well for this action.
3. Use the Text and Image checkboxes on the button row to control whether the label, the icon, or both are shown.

5. Reorder, preview, and publish

1. Drag the button by its move handle (the up/down arrows) to set where it appears.
2. Now see it work. Use App Setup → Previewer to scan the QR code and try the button in the WPMAM Previewer app — tapping it should take you straight to your app’s notification settings on the device.
3. When it’s working the way you want, click publish to push the change live. No App Store / Play Store rebuild needed.

Notes and gotchas

• One-time prompt. Since the OS only asks once, this button is really the only reliable way to bring back a user who declined. It’s worth pairing with an onboarding screen that makes the case for notifications before the OS ever asks.
• Behavior is the device’s, not the app’s. What the user sees after tapping is the operating system’s own notification settings screen for your app — so the exact layout will differ between iOS and Android, and even between OS versions.
• Per-role and per-placement. A button added on the Home Page for one role lives independently from one on the Left Menu, or one for another role. If it seems to have “disappeared,” check that you’re looking at the same role and placement you created it under.
• Deleting it. No harm in deleting — the Delete Button link in the button’s expanded options only removes it from that one placement and role.

Related

• Add a new screen (button) to your app — the general flow for placing any button, with all the content types.
• Enable Location Services button — the sibling action button that hands off to the device’s location-permission settings.
• Set up the bottom tab bar for your app — placing and ordering buttons in the tab bar.
• Building Your App: Configure your app’s home screen — arranging the home grid and left menu.

What’s next

A button to opt in only matters once there’s something to opt into. If you haven’t already, set up your push-notification provider, and consider adding an onboarding screen that explains why notifications matter — together they make this button far more effective. Then preview it, and publish.