Inviting your team and what each role can do
People join your agency by invitation. There is no way to add a colleague by typing their name — they receive an email, sign in with that address, and accept.
Sending an invitation
Go to Settings → Team. If you are an owner or an admin you will see a form above the member list:
- Enter the colleague's email address.
- Choose Member or Admin in the dropdown.
- Press Send invite.
The invitation appears under Pending invitations with the role you chose and a Revoke link. It expires after seven days. Inviting the same address again re-issues the existing invitation with a fresh link rather than creating a second one, so a lost email is fixed by simply inviting again.
Members see the list of colleagues, but not the invite form or the revoke and remove controls.
Accepting
The email links to an acceptance page showing the agency name and the role offered. The invitee must be signed in with the invited address. If they are signed in as someone else the page says so, names both addresses, and offers to sign in with a different account. They can accept or decline.
Accepting creates the membership and switches them into your agency. Nobody is ever granted ownership by accepting an invitation.
What each role can do
Everyone with a membership can do the day-to-day work: create and edit trips, add travellers, load itineraries, upload documents, read conversations and reply to travellers.
Restricted to owners and admins:
- Deleting a trip.
- Deleting a contact from the CRM.
- Saving branding under Settings — the agency name, logo, colours, contact details, bot token, review link, brief hour and quiet hours.
- Reading the audit log of who changed what.
- Creating and revoking API keys for the chat assistant connector.
- Inviting, revoking, removing members and changing roles.
Restricted to owners alone:
- Granting the owner role. An admin can promote someone to admin, but not to owner.
Two safety rules apply regardless of role. The last owner cannot be removed, so an agency can never end up with nobody in charge. And anyone can remove themselves — leaving is not an administrative action.
Removing someone
Press Remove next to their name. It takes effect immediately: their access to the agency's trips, travellers, documents and conversations ends. Owners cannot be removed this way; change their role first, or have them leave.
Removing a colleague does not delete anything they created. Trips, notes and messages belong to the agency, not to the person who typed them.
Belonging to more than one agency
A single account can be a member of several agencies — useful for a consultant, or for an agency that keeps a separate workspace for a subsidiary. Switch between them under Settings → Agency & language. Everything you see, and everything you can query through the API or the chat assistant, is scoped to whichever agency is active at that moment. There is no view that spans two.
Choosing roles in practice
Make the people who own the business owners, and there should usually be at least two so nobody is locked out during a holiday. Make anyone who configures the product — branding, automations, the bot — an admin. Everyone who books and runs trips can be a member; the restricted list above is deliberately short, and none of it is needed to operate a departure.
Every change made through the API is recorded. For what is stored, where, and how tenants are isolated, see where your data lives, and who can see it. To get started on the operational side, see load your first trip and your brand, your channel.