Notifications

TiniVault notifies you when a schedule or trigger fires the Notify action. Notifications appear in two places:

• In-app inbox — the bell icon in the top header. A red badge shows the unread count.
• Web Push — your browser pops a system notification even when TiniVault is closed.

How It Works

Any schedule or trigger with a Notify action creates a notification when it runs. Each member of the household gets one row in their own inbox per firing — there's no shared queue.

Click a notification row and TiniVault opens the linked item with the firing schedule auto-expanded so you can see exactly what changed.

The Bell

The bell lives next to your user menu in the top header.

• Badge — unread count. Shows 9+ if you have more than nine.
• Click — opens the dropdown panel.
• Dropdown actions:
  • Push toggle — Enable / Pause / state badge.
  • Mark all read — clears the badge without removing rows.
  • Per-row swipe — left to delete (with a 5-second undo), right to flip read/unread.
  • Clear read — bulk-deletes everything you've already read; unread rows are untouched.

Enable Push on This Device

Push delivers notifications to your OS even when TiniVault isn't open in any tab. Each browser on each device subscribes separately — enabling it on your laptop doesn't enable it on your phone.

1. Open the bell.
2. Click Enable push at the top of the dropdown.
3. Accept the browser permission prompt.

The toggle now reads Push: On. Test by firing a schedule due today — you should see a system notification a few seconds later.

Pause vs Block

• Pause is per-device, set from inside TiniVault. Other devices keep delivering. Resume any time.
• Block is the browser-level permission state. If you click "Block" in the permission prompt, TiniVault can't ask again — you'll need to clear the site permission in your browser settings to recover.

Pause on a Device

Don't want push at work? Open the bell, click Push: On, and choose Pause. The toggle flips to 🔕 Paused. Your subscription is removed from the server but a local flag remembers your choice — re-enabling re-subscribes silently.

In-app inbox notifications still arrive while paused; only the OS-level pop-up is suppressed.

iOS Safari (PWA Required)

iOS only delivers Web Push to installed PWAs. Desktop / mobile Safari without "Add to Home Screen" cannot subscribe.

1. Open TiniVault in Safari.
2. Tap the share button → Add to Home Screen.
3. Open TiniVault from the home-screen icon (not the Safari app).
4. Sign in if needed.
5. Tap the bell → Enable push.

If the Enable push button is greyed out and reads "unsupported", the page is loaded outside the home-screen launcher. Re-launch from the icon and try again.

Troubleshooting

"Push blocked" You denied the permission prompt at some point. Reset the site permission in your browser settings (Privacy → Site Settings → Notifications → find your TiniVault domain → Allow), then click Enable push again.

No notifications arriving despite "Push: On"

• Check the OS-level Do Not Disturb / Focus mode is off.
• Confirm the schedule's date is today and its action list includes Notify.
• Confirm the schedule status is active (not success from a previous firing — schedules only fire once unless re-armed).

Push works on one device but not another Subscriptions are per-browser-per-device. Enable on each device separately. A new browser profile, an incognito window, or a re-installed app counts as a new device.

Stale subscriptions after browser profile reset TiniVault automatically prunes dead push endpoints on the next firing — you don't need to clean up manually. The next round of notifications stops trying to deliver to the old endpoint.

HTTP (non-HTTPS) deployments Web Push requires a secure context (HTTPS, or localhost for development). Self-hosted deployments behind a non-HTTPS reverse proxy can't subscribe. The bell badge still works (it's plain HTTP polling), but the Enable push button shows unsupported.

Privacy

• Notification rows are stored on your TiniVault server only. They never leave your deployment.
• Web Push delivery routes encrypted payloads through your browser vendor's push service (FCM for Chrome / Edge, Mozilla autopush for Firefox, Apple for Safari, WNS for Edge UWP). The push services see encrypted blobs only — they cannot read titles or bodies.
• VAPID keys (the long-lived signing identity) are stored in your TiniVault database. Re-installing without a backup invalidates every existing push subscription; clients re-subscribe automatically on the next visit.