People and travelers
A person is a traveler in the ledger. A member is someone with a login who can open that ledger. Those are different lists.
Each ledger has one “self” traveler created for the owner. Residency and Schengen default to that person. Use the person selector on those pages to see totals for someone else in the same ledger.
Limits
Section titled “Limits”Up to 6 people per ledger during trial and with lifetime access. Adding people never restarts the trial. After expiry, all people and their records remain readable.
Tag who traveled on a journey (and on stays). Day counts for a person only include journeys they are on.
Connected assistants
Section titled “Connected assistants”TripLedger’s MCP server can work with people as well:
list_peoplereturns traveler IDs.- Journey and stay reads return their participants and can be filtered by
personId. - Journey and stay writes accept
participantIds. - Residency, Schengen, travel-summary, current-country, and gap tools accept
personId. - Expense reads and writes expose the optional
payerPersonId.
Use an ID returned by list_people; a person must belong to the connected ledger.
Members (owner, editor, viewer) are covered in Ledgers and invitations.
Optional analytics
Allow analytics cookies to help us understand which help pages are useful? See the Privacy Policy.