Four roles, invite links, and a way to check what your group sees before you send it.
A trip has an organiser, some people riding it, and usually a few following from home. Participants gives each of them exactly the access their part needs, without a permissions matrix nobody wants to configure.
Owner and editor change the plan. Riders are on the trip: they tick their own packing and tasks, log progress and expenses, and post photos, but cannot rewrite the route. Viewers read — a partner at home who wants the detail without edit rights.
The distinction between a rider and a viewer also drives the maths: viewers are excluded from expense splits and from per-person checklists.
Knowing what your group will see normally means creating a second account and inviting yourself. Instead there is a toggle that re-renders the entire app read-only, exactly as a rider or viewer gets it.
It is a view-only lens over the interface, not a security boundary — the database still enforces the real permissions underneath. It exists so you can check the experience before you send the invite.
One multi-tool between three people, but a rain jacket each. The list knows the difference…
Read more →💸Log what you paid and who it covered. The balances do the rest.…
Read more →🔴One public link for everyone at home, and precise control over what it reveals.…
Read more →Free while in early access. A couple of minutes to set up.