# Enable Notifications And Test Push

Use this guide to set up notifications for your account.

## Before you start

* Use a supported browser with push capability.
* Allow browser notification permission when prompted.

## Steps

1. Open `Dashboard > Notifications`.
2. Click `Enable push notifications`.
3. Once enabled, click `Send test push`.
4. Confirm test message arrives on your device/browser.
5. Expand each category and toggle the alerts you want.

## Categories you can configure

* Team
* Bookings
* Scheduling
* System and billing

## Notes

* Preferences save automatically.
* If push is disabled, category toggles are visually present but not actionable.

## If something does not work

* Push unsupported message: switch to a supported browser/device.
* No test push received: verify system notification permissions and service-worker support.

## Dev-only key simulation (one-by-one testing)

Use this only in non-production environments.

1. Enable the target preference in `Dashboard > Notifications`.
2. Call `POST /api/push/simulate` with:

```json
{
  "preferenceKey": "locus_resource_availability"
}
```

3. If you need to test delivery plumbing while preference is disabled, send:

```json
{
  "preferenceKey": "locus_resource_availability",
  "bypassPreference": true
}
```

The route returns delivery counts for Web Push and FCM, plus cleanup counts for expired tokens/subscriptions.

## Screenshot Checklist (GitBook Publishing)

* [ ] Capture notifications page with push status panel visible.
* [ ] Capture enable-push action state.
* [ ] Capture successful test push confirmation state.
* [ ] Capture category toggles expanded for at least one group.
* [ ] Redact user/device-identifying details if shown.

## Screenshot Placeholders

* `TG-NOTIFS-01-context`: Notifications page with push panel.
* `TG-NOTIFS-02-action`: Enable push flow or permission prompt context.
* `TG-NOTIFS-03-result`: Test push success message.
* `TG-NOTIFS-04-preferences`: Expanded category with toggles enabled.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://xdbx.gitbook.io/axon/task-guides/enable-notifications-and-test-push.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.