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.2 KiB
Admin — Addons
The Addons tab lets you enable or disable optional features for the entire TREK instance. Toggling an addon affects all users immediately — disabling one hides its UI elements and blocks its API routes instance-wide.
What addons control
Each addon toggle controls a feature set. When you disable an addon, users lose access to that feature everywhere in the app. No data is deleted; re-enabling the addon restores access to existing data.
Addon categories
Addons are grouped into three categories, shown as labeled sections.
Trip addons
Trip addons add per-trip feature panels. They appear in every trip where the addon is enabled.
The default trip addons are: Lists, Costs, Documents, Collab, and Naver List Import (all enabled by default). The exact list is determined by what is registered in your TREK database.
Sub-toggles on trip addons:
- Lists — when enabled, a nested Bag Tracking toggle appears. Bag Tracking lets users assign packed items to specific bags.
- Collab — when enabled, four sub-toggles appear for individual collaboration features:
- Chat — in-trip real-time chat
- Notes — shared trip notes
- Polls — trip polls
- What's Next — the "what's next" widget
Each sub-toggle can be disabled independently while the parent addon remains enabled.
Global addons
Global addons add features that are not tied to a single trip. The default global addons are Vacay, Atlas, Collections, and Journey.
- Vacay — personal vacation day planner with calendar view. Enabled by default.
- Atlas — world map of visited countries with travel stats. Enabled by default.
- Collections — personal place library: save places across trips into named lists, copy them into any trip, and share them. Disabled by default. See Collections.
- Journey — trip tracking and travel journal (check-ins, photos, daily stories). Disabled by default.
Sub-items on global addons:
- The Journey addon shows photo provider toggles underneath it. Each photo provider (e.g., Immich, Synology Photos) can be enabled or disabled independently.
Integration addons
Integration addons connect TREK to external services. Most of them need additional configuration (API keys, URLs) once enabled, but not in the admin Settings tab — each one has its own place.
- The MCP addon requires
APP_URLto be set in your environment. When enabled, the MCP Access tab appears in the Admin Panel. Disabled by default. See MCP-Overview for full details. - The AirTrail addon syncs flights from a self-hosted AirTrail instance. Disabled by default. The toggle here is the instance-wide switch only; each user connects their own instance (URL + API key) in Settings → Integrations.
- The AI Parsing addon is the LLM fallback for booking imports KItinerary cannot read. Disabled by default. When enabled, its provider, base URL, API key, and model fields appear inline underneath the addon row. Filling them in sets the instance-wide config for all users; leaving them blank lets each user configure their own provider in Settings → Integrations. See AI-Booking-Import.
Enabling or disabling an addon
Click the toggle switch on any addon row. The change is applied immediately — no save button is needed. A brief success toast confirms the update.
If a toggle fails (e.g., network error), it rolls back to its previous state.
Additional configuration
Some addons require credentials or environment variables before they are functional:
- Journey — works without any external integration. To embed photos from Immich or Synology Photos, enable the corresponding photo-provider toggle listed under Journey, then configure credentials per-user in Settings → Integrations. See Photo-Providers.
- MCP — requires
APP_URLto be set so OAuth redirect URIs resolve correctly.