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.
4.6 KiB
Creating a Trip
Opening the Dialog
On desktop, click the floating New Trip button in the bottom-right corner of the dashboard, or the dashed New Trip tile at the end of the trip grid, to open the Create New Trip dialog. On mobile the floating button is replaced by the + in the centre of the bottom tab bar, and an empty dashboard also offers a Create First Trip button.
You can also open it directly via a deep link: navigate to /dashboard?create=1. This is the URL used by system notices that prompt you to create a trip.
Fields
Title (required)
The trip name. Cannot be empty — saving is blocked until a title is entered.
Description (optional)
A short free-text description shown on the trip card.
Dates
Set a Start date and End date using the date picker. The day count is calculated automatically when both are set.
If you leave both dates empty, a separate Day count field appears. Enter a number between 1 and 365 to create a date-less itinerary with a fixed number of days.
You cannot set only one date and leave the other blank via normal interaction — setting a start date auto-fills or adjusts the end date to preserve the previous duration.
Currency
The trip's currency — its accounting base. Every expense in the Costs tab is converted into it, and every balance and settle-up suggestion is calculated in it. The dialog pre-fills your own display currency (Settings → General → Display currency); if you left that on Trip currency, it falls back to EUR. An administrator can preset the instance-wide value under Admin → User Defaults, which new users inherit until they pick their own. 165 currencies are available.
Pick the currency you will actually settle up in. It is not a cosmetic label, but it is not a one-way door either: you can change it later from the same dialog (with the trip_edit permission), and TREK re-bases the existing expenses so no money moves — see Currencies → Changing the trip currency.
This is not the same as the display currency in Settings → General, which changes what you read on trips that already exist. See Currencies.
Cover Image
The cover image is displayed on the trip card and as the background of the Spotlight card. You can add one in three ways:
- Drag and drop an image file onto the dashed upload area.
- Paste from clipboard — if you have an image in your clipboard, paste it anywhere in the dialog.
- File picker — click the upload area to browse for a file.
- Search Unsplash — type a query to pick a stock photo. If this returns "Unsplash search unavailable" (common on VPS/datacenter IPs), configure a free Unsplash Access Key — see Environment-Variables → Image Search (Unsplash).
When creating a new trip the cover image field is always visible. When editing an existing trip it is only shown if you have the trip_cover_upload permission. For a new trip, the image is uploaded immediately after the trip is created.
Reminder
A push notification sent before the trip departs. The field shows a set of preset options:
| Option | Days before departure |
|---|---|
| None | 0 |
| 1 day | 1 |
| 3 days | 3 |
| 9 days | 9 |
| Custom | 1–30 (you enter the number) |
When creating a new trip the reminder field is always visible. When editing an existing trip it is only shown to the trip owner or admin users.
If reminders are disabled on your instance (trip_reminders_enabled = false), the reminder section is shown at reduced opacity with an informational message in place of the preset buttons.
Admin: Trip reminders are controlled by a server-side feature flag (
trip_reminders_enabled). Contact your administrator to enable them.
Members
Add initial trip members from the members selector. On a new trip, selected members are queued locally and added to the trip immediately after it is saved. The selector shows all registered users on your instance except yourself.
Saving
Click Create New Trip. The trip is saved, the dialog closes and a "Trip created successfully!" toast confirms it — you stay on the dashboard. The new trip is sorted into the trip list by its dates; click its card (or the Spotlight card, if it is the trip that earns that spot) to open the Trip-Planner-Overview.