Files
TREK/wiki/Addons-Overview.md
T
Maurice 44c92052a3 docs(wiki): bring the pages in line with 4.3.0
Every page was read against the code on dev. What changed:

- Pages that described 4.2 behaviour: satellite view on the vector maps,
  the mobile journal timeline, Collab with its fifth tab, the Review badge,
  clustered pins on the share page, the Leaflet preset list, the strict
  guard on fe80::/10, the invite link tools and their scopes, the Public
  API scope rules, the permission count in the plugin SDK.
- Features of this release that no page mentioned: videos in a journal
  entry, receipts on an expense, the Google transit backend, routing
  counters, the rating on a place, the navigation menu, car stops, the
  manual school holiday catalogue and its MCP tools, the Dawarich panel in
  the Atlas, the release notes modal, plugin frames going fullscreen, the
  corridor call into the search provider hook.
- Statements that sent an admin the wrong way: DEFAULT_LANGUAGE is not in
  the Helm ConfigMap, env.PORT cannot be changed on the chart alone, the
  rotation script does not cover the document sync credentials, event
  handlers cannot broadcast, there is no per user MFA reset in the admin
  panel, the demo user can edit, an unparsable APP_URL stops the server.
- Updating gets a section for 4.3.0: the TREK Places API as the new
  default, the new variables, the Overpass timeout, SSO sessions on an
  OIDC only instance, the migration that puts booked nights on the drive.
2026-09-20 12:11:41 +02:00

3.8 KiB

Addons Overview

Addons are optional features that an admin can enable or disable for the entire TREK instance. When an addon is disabled, its navigation tabs, menu items, and API routes are hidden from all users.

Addon overview

What addons are

Each addon extends TREK with functionality beyond the core trip-planning features. Addons are managed globally: you cannot enable an addon for one user only. Once enabled, the feature becomes available to all users on the instance.

Addon list

The following addons are registered in the system (defined in server/src/db/seeds.ts; the TypeScript constant ADDON_IDS in server/src/addons.ts covers all addons except naver_list_import):

Addon ID Type Description
mcp integration Exposes TREK data and actions through the Model Context Protocol for AI assistant integrations.
packing trip Lists: packing lists and to-do tasks for your trips. See Packing-Lists.
budget trip Costs: track and split trip expenses. See Budget-Tracking.
documents trip Document and file attachments for trips: itineraries, visa copies and other files. Can be kept in step with a self-hosted document store (Paperless-ngx, Papra, Nextcloud, OpenCloud, Synology). See Documents-and-Files and Document-Sync.
vacay global Personal vacation day planner with a year calendar, holiday packs, collaborator fusion, and read-only calendar sharing. See Vacay.
atlas global Interactive world map showing countries and regions you have visited, plus a bucket list. See Atlas.
collab trip Notes, polls, and live chat for trip collaboration. See Real-Time-Collaboration.
roadtrip trip Road trip: plans a trip as one continuous drive, with stops along the route, driving times and arrival times that update themselves. Off by default. See Road-Trip.
journey global Trip tracking and travel journal: check-ins, photos, and daily stories. See Journey-Journal.
collections global A personal, server-wide library of saved places in named lists, with idea/want/visited status, categories, and fusion sharing with per-member roles. See Collections.
airtrail integration Sync flights from your self-hosted AirTrail instance into trips.
dawarich integration Read the stays and recorded routes of each user's own Dawarich instance, offered as suggestions to confirm. Read-only, nothing is written back. See Dawarich.
llm_parsing integration AI Parsing: an LLM fallback that extracts bookings from confirmation files KDE Itinerary can't read. See AI-Booking-Import.
naver_list_import integration Import places from shared Naver Maps lists directly into a trip.

Enabling addons

Admin: all addons are toggled from the admin panel. Navigate to Admin-Addons to enable or disable individual addons for your instance.

Per-addon sub-features

Some addons expose sub-features that an admin can independently toggle. The Real-Time-Collaboration addon, for example, lets an admin decide which of its five sub-features (chat, notes, links, polls, and what's next) are active across the instance. These are configured from the Admin-Addons panel alongside the addon's main toggle.

The Documents addon carries one switch per document store: Paperless-ngx, Papra, Nextcloud, OpenCloud and Synology Drive. They are off by default and only show while Documents is on, and switching Documents off switches all of them off. The stores themselves are connected per trip, in the trip's file manager. See Document-Sync.