Plan a trip with other people without losing the thread
Invites, editor and viewer roles, real-time edits and read-only share links — how collaboration works in Gullivr, and when to use which.
Pasquale Carbone 3 min read
Group trips break in a predictable way. One person builds the itinerary, everyone else sends suggestions in a chat, and by day three nobody is sure which version is the real one.
Gullivr has three separate answers to that, and picking the wrong one is the usual reason people find it confusing. Here they are, shortest first.
A share link, for people who only need to look
Turn on sharing for a trip and you get a public read-only link. Anyone with the URL sees the itinerary as it stands — days, places, times — without an account and without being able to change anything.
Use it for the people who are coming but not planning: parents who want to know where you'll be, a friend joining for two days, the group chat that just wants the address of the hotel. Turn sharing off and the link stops working.
An invite, for people who are actually planning
Inviting a collaborator by email adds them to the trip properly. They get one of two roles:
- Editor — can add and move places, edit days, add flights and accommodation, change anything you can change.
- Viewer — sees everything inside the app, including the parts the public link does not show, but cannot edit.
Roles are not permanent. Promote a viewer to editor when they start pulling their weight, or demote an editor who keeps reordering day 4. You can also cancel an invitation before it is accepted, and remove a collaborator afterwards.
The rule of thumb: editor for the two or three people building the plan, viewer for everyone else. A trip with six editors is a trip where nobody knows who moved the museum.
Edits show up as they happen
When two people have the same trip open, changes appear on both screens without a refresh. This matters more than it sounds like it should: the reason collaborative planning usually happens in a chat window is that people do not trust a shared document to be current. Watching a place land on day 2 while someone else adds it removes that doubt.
Where the AI agent fits
If you have connected an AI agent, it acts with your permissions on your trips. So "ask Claude to find three restaurants near the hotel and add them to day 3" produces edits your collaborators see immediately, the same as if you had added them by hand.
Which is the actual point: the agent is another editor on the trip, not a separate app you have to copy results out of.
The short version
| You want | Use |
|---|---|
| Someone to see the plan | Share link |
| Someone to see everything, in the app | Invite as viewer |
| Someone to help build it | Invite as editor |
| An AI to help build it | Connect an agent |