Trips

Storing documents and passes

Travel files (tickets, confirmations, boarding passes, scans) stay attached to the things they belong to. This page covers where files can live and who sees what. For where the bytes are stored, see Storage backends.

The four places a file can live

  • On an item. The boarding pass on a flight, the booking confirmation on a hotel. Added from the item's detail panel and visible to anyone who can see that item.
  • On a trip. Cross-item paperwork like a master itinerary. Added from the trip's Files tab and visible to anyone who can see the trip.
  • In a constellation. Shared with every member of a group (a villa contract, a group booking). Added from the constellation's page.
  • In the private stash. Personal documents tied to nothing: passport scan, driving licence, insurance card. Added under Settings → Travel profile, in the Documents vault.

The private stash is exactly that. Files there are visible to their owner and no one else, and no toggle exposes them to a constellation. The one way out is your own choice: adding a document to a trip (below) shows it, with its scan, to the people on that trip.

Documents on trips and in your documents

A document (a visa, an eSIM, an insurance policy) is one thing, kept in one of two ways, and it can be on several trips at once: the same ESTA on every US trip, say. Open the document and look under Attached to:

  • Your documents on: it's yours rather than any one trip's. It's listed under Settings → Travel profile → Documents and counts for every trip you take: a visa or eSIM there stops the "visa or entry permit?" and "mobile data or eSIM?" prompts for its country, and its expiry date is checked against each trip.
  • Your documents off: it belongs to the trips it's on and counts only for those. Switching it off needs it to be on a trip first ("Add it to a trip first."); it then belongs to the earliest of them and stays on the rest.
  • Each trip it's on is listed; the × takes it off that one. A trip document has to stay somewhere, so taking it off its last trip is refused until it's on another trip or in your documents.
  • Add to a trip… puts it on another of your trips, past ones included, or on a trip you plan for someone who lets you plan trips for them (their trip, with you on it as an editor). It shows there for everyone on that trip, them included. Other people's trips aren't offered: "You can add it to your own trips, and to trips of people who let you plan for them."

Only the person who added a document sees these controls. Everyone on a trip sees the documents on it, the same as before.

For item- and trip-scope files, a per-file visibility flag controls whether people viewing the trip through a constellation share see the file. People on the trip see them regardless.

After adding one

Adding a file — uploaded or pasted as a link — ends on a confirmation naming what was added, with View file to open it and a link to where it landed. Add another starts the next one without reopening anything.

A file added to a constellation says it's been sent for review: an admin of that constellation approves it before other members can see it.

One file, several items

A single PDF often covers several things: one airline confirmation for both legs, one receipt across two events. A file can be linked to multiple items when added, and shows up on each of them. Deleting it once removes it everywhere.

Constellation files and review

In a constellation, uploads are visible to everyone, so uploads from members start pending and a constellation admin approves or rejects them before they go live for the group. Admin uploads skip the queue and publish immediately. A rejected upload stays visible to its uploader with the reason.

Boarding passes and Apple Wallet

A .pkpass file (the format airline apps and emails use for boarding passes) is recognised when attached: on an iPhone the file opens straight into Apple Wallet. Passes stored this way are static and don't refresh if the airline reissues the pass.

Files from forwarded emails

When a forwarded confirmation is recognised, its attachments are saved to the matching item automatically; the ticket PDF lands on the flight by itself. Parts of the email itself, such as an email signature or a small logo in the message, aren't saved. This uses the default storage backend and can be turned off under Settings → Cloud storage ("Auto-save email attachments").

Having them without signal

Documents for the trip underway and the next trip are saved to the device automatically, so they open on landing before a SIM or roaming plan is sorted. That covers files on an item, files on the trip, and receipts on expenses alike.

A file already on the device shows a Downloaded mark next to its name. A file without the mark still opens normally with a connection. See Installing the app for what else is kept and when it refreshes.

Size limits

Individual files are capped at 25 MB. Files stored in Constellations' own storage (rather than a personal Google Drive) count toward an account-wide quota. See Storage backends.

Storing documents and passes · Constellations