Maurice
7da0080557
* docs(wiki): correct the install and operations pages for 4.0.0 Quick Start passed docker an empty ENCRYPTION_KEY: an assignment prefix is not expanded on the same command line, so the server silently generated its own key instead of taking the one the page told you to set. The tag examples pinned to the 3.x line, the documented tmpfs size did not match the shipped compose file, and several .env values were described as reaching the container when compose never interpolates them. * docs(wiki): match the MCP reference to the registered surface The scope table was missing the whole Collections group and the totals said 27 scopes across 13 groups where the code registers 29 across 14. The Cloudflare link on the setup page pointed at an anchor on its own page instead of the heading on Troubleshooting. * docs(wiki): correct the plugin and admin pages Three links to Plugin-Development carried a .md suffix, which does not resolve on the wiki. The admin pages described tabs, permissions and storage behaviour that had moved on. * docs(wiki): bring the feature pages back in line with the app Costs still documented the old panel, where categories could be added, renamed, reordered and deleted; they are fixed now and the panel is a day-grouped ledger with settlements. Trip sharing, journeys, maps, packing, reservations and the account pages had all drifted in the same way. * docs(wiki): cover the pages the first pass did not reach The MCP catalog listed 168 of the 201 registered tools; the settlement tools and rate_place were missing here and the Collections family from the addon page. Several resource rows claimed a trips:* scope where the handler asks for trips:read. * docs(wiki): tighten the corrections a review picked apart The audit-log resource is the row id, not the credential id; an admin password reset does not bump password_version the way the page implied; and a few of the new paragraphs described behaviour more confidently than the code supports. * docs(wiki): fix what a last read-through caught Costs shows every figure in your display currency, not the trip's, and an expense with no payer still counts against the members it is split between. Studio's cutoff is a 1024px viewport rather than phones alone, and the Integrations tab is gated on the providers an admin has configured. * docs(wiki): the last few the review caught A passkey satisfies the MFA policy everywhere except the WebSocket handshake, which still asks for TOTP, so a passkey-only account under that policy gets no live updates. Mobile optimizes a day from two places, not three. The ctx.db row carried an unescaped pipe that split the table, and the Backups table linked with a wiki link whose pipe did the same.
5.8 KiB
Notifications
The Notifications tab (Settings → Notifications) lets you choose which events notify you and through which channels. Each toggle saves immediately.
Notification channels
TREK ships four delivery channels, and a plugin can add more. Which channels appear depends on what the admin has enabled server-side.
| Channel | Description |
|---|---|
| In-app | Bell icon in the navigation bar. Always available. Delivered in real time via WebSocket. |
| Delivered to your account email. Requires the admin to configure SMTP. | |
| Webhook | TREK POSTs a JSON payload to a URL you specify. Discord and Slack webhook URLs are auto-detected and receive a natively formatted payload. |
| ntfy | Push notifications via ntfy.sh or a self-hosted ntfy server. |
Plugin channels
A plugin can register an additional channel — Gotify, Pushover, Telegram, anything that
takes a message — by implementing the notificationChannel hook. See
Plugin-Development.
Once the admin installs the plugin and switches its channel on, it appears as a new column in the preferences matrix beside Email and In-App, and behaves like any other channel: each user supplies their own credentials (in the plugin's own settings) and picks per-event which notifications they want on it.
Two things are true of plugin channels specifically:
- They are user-scoped. Admin-only events (like
version_available) always go out over the built-in admin channels, never a plugin's. - The plugin never sees your trips. The notification is rendered by TREK — in your language, with the deep link already built — before the plugin is handed it. The plugin gets that message and your own credentials for its service, and nothing else.
Notification events
The following events are configurable in user settings:
| Event | Description |
|---|---|
trip_invite |
Someone invited you to a trip |
booking_change |
A booking was added, updated, or removed in a trip you're part of |
trip_reminder |
Reminder before a trip starts |
todo_due |
A to-do assigned to you, or in a trip you're part of, is due soon |
vacay_invite |
You were invited to fuse vacation plans |
vacay_share |
Someone shared their vacation calendar with you (view only) |
collection_invite |
Someone invited you to share a collection |
photos_shared |
Photos were shared with a trip |
collab_message |
A new message in a collaborative trip |
packing_tagged |
You were assigned to a packing category in a trip |
plugin_notification |
An installed plugin sent you a notification (only plugins granted the notify:send capability can do this) |
All user-facing events support all four channels (in-app, email, webhook, ntfy). A dash (—) in the matrix means that channel/event combination is not implemented.
Admin-only events
The following events are shown in the admin panel (Admin → Notifications) and are not configurable per user:
| Event | Description | Channels |
|---|---|---|
version_available |
A new TREK version is available | in-app, email, webhook, ntfy |
replica_failure |
A write to a storage replica failed (repeats within the hour are suppressed and counted) | in-app, email, webhook, ntfy |
In-app-only events
The following event is fired automatically and can only be delivered in-app — it appears in the preferences matrix with an In-app toggle and a dash in every other column:
| Event | Description | Channels |
|---|---|---|
synology_session_cleared |
Your Synology account or URL changed, clearing your Photos session | in-app only |
Configuring the matrix
The preferences panel shows a grid of events × channels. Toggle each intersection independently. Changes are saved automatically.
Webhook configuration
Enter a URL that TREK will POST to when a notification fires. Once saved, the URL is displayed as ••••••••. Use the Test button to send a test payload to the saved URL.
TREK auto-detects the webhook destination and adjusts the payload format:
- Discord (
discord.com/api/webhooks/…) — sends a rich embed with title, description, and a timestamp. - Slack (
hooks.slack.com/…) — sends a formatted Slack message block. - Generic — sends a plain JSON object with
event,title,body,tripName,link,timestamp, andsource("TREK") fields.
ntfy configuration
Enter your ntfy topic and optionally a custom server URL (defaults to the server-wide ntfy server set by the admin) and an access token for private topics. The token is stored encrypted and displayed as •••••••• after saving. Use the Test button to verify delivery.
In-app notification center
The bell icon in the navigation bar shows your unread notification count. Click it to open the notification panel where you can:
- Mark individual items read or unread.
- Mark all notifications read at once.
- Delete individual notifications or clear all at once.
- Respond to boolean notifications (e.g. trip invites that offer Accept / Decline actions directly in the panel).
In-app notifications are pushed in real time via WebSocket so the badge and panel update without a page refresh.
Per-trip preferences
Notification preferences are configured globally in Settings → Notifications. There are no per-trip overrides — the same toggle applies across all trips.