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

# Push notifications

> Browser and mobile push — the channel that actually pages someone.

Push is what makes aciona.me work at 3 a.m. It comes in three forms: browser, Android and iOS.

## Browser push

Works in the web dashboard. On your first visit, the browser asks permission to send notifications — accept it.

<Steps>
  <Step title="Allow notifications">
    If you declined before, you have to re-enable it in the browser's site settings. aciona.me cannot ask again after a refusal.
  </Step>

  <Step title="Keep the browser open or in the background">
    Browser push is delivered by the service worker; the browser must be running (the tab does not have to be open).
  </Step>
</Steps>

<Note>
  Browser push is great during working hours and not enough outside them. For overnight on-call, use the mobile app.
</Note>

## Mobile push

<Tabs>
  <Tab title="Android">
    aciona.me uses a dedicated notification channel for `critical` incidents, with:

    * **Its own alarm sound**, distinct from ordinary notifications.
    * **Do Not Disturb bypass**, once you grant the matching permission.
    * **Full-screen notification**, so the incident shows up even on a locked phone.

    <Warning>
      Do Not Disturb bypass requires an explicit authorization in Android settings. Without it, critical incidents get silenced along with everything else.
    </Warning>
  </Tab>

  <Tab title="iOS">
    aciona.me sends **time-sensitive** notifications, which break through scheduled summaries and appear on the lock screen.

    When the device supports it and the feature is enabled, `critical` incidents can use **Critical Alerts**, which ring even with the phone on silent — this requires the user to grant explicit authorization on the device.
  </Tab>
</Tabs>

## Severity and push

<Warning>
  Incidents with `info` severity **do not generate push**. The attempt is recorded with a severity-suppressed status.
</Warning>

This is a deliberate hygiene decision: informational alerts should not wake anyone. If something needs a page, send it with `warning` severity or above.

## Acting from the notification

Tapping the notification opens the incident in the app through a direct deep link — no scrolling through a list. From there you can acknowledge, take ownership or resolve.

## Quick diagnosis

| Symptom                             | Likely cause                                                                    |
| ----------------------------------- | ------------------------------------------------------------------------------- |
| No push at all, on any device       | Push snoozed in account preferences                                             |
| Push on desktop, not on mobile      | App not installed, not signed in, or system permission denied                   |
| Push arrives but is silent at night | Do Not Disturb without bypass (Android) or Critical Alerts not authorized (iOS) |
| Only `info` incidents missing       | Expected behavior — `info` does not generate push                               |

<Card title="I did not get a notification" icon="life-buoy" horizontal href="/en/troubleshooting/notification-not-received" />