Part of Operations
Inviting your office
A Kathmandu office often has a director, two or three people answering WhatsApp and email, someone running operations from the warehouse in Thamel, and a writer who looks after the website. Each gets their own login in TripNerve rather than sharing one, so every enquiry, booking change and published page is recorded under a real name.
On the Team screen, choose Invite member, type an email and pick a role. The invitation arrives by email and shows who sent it and the role. Pending invitations are listed with an expiry date, and you can resend or cancel them. The person who sent the invitation gets a push notification on the TripNerve app when it's accepted.
The starter roles
Every company starts with four roles so the first invitation doesn't mean building one from scratch. The person who created the company is the Owner, who can do everything; that role can't be changed.
- Manager: runs the business day to day, with everything except changing roles
- Sales: works enquiries, customers and bookings, sees departures, reports and promo codes
- Operations: builds and publishes trips, runs departures, manages crew, vehicles and accommodation, and sees bookings
- Viewer: can look at bookings, enquiries, customers, departures, crew, reports and more, and change nothing
Building a role of your own
A role is a set of permissions you tick, grouped by area: trips, departures, bookings, crew and vehicles, accommodation, promo codes, customers, enquiries, media, website, translations, analytics, reports, blog, newsletter, company, team and roles. A content writer role might write and edit blog posts and edit the website without publishing either, so a manager checks the page before it goes live.
You can only give out permissions you hold yourself, so a manager can't build a role more powerful than their own. Change a role and everyone who holds it gets the change. Ask AI and the ChatGPT and Claude connectors work within the same permissions as the person using them.
When people change jobs or leave
Staff turnover in a Thamel office is a fact of the off-season. When a salesperson moves into operations, change their role on the Team screen and the new access applies straight away. When someone leaves, remove them: they lose access to the company at once, while the enquiries they worked and the bookings they took stay where they were.
Roles also decide what reaches each person. Push notifications about new enquiries and bookings go to people whose role can see them, and the morning email and push lists only what that person's role covers: follow-ups for sales, short departures for operations, the tourism licence for whoever can edit company details.
Signing in, and keeping companies apart
People sign in with an email and password, with Google, or with a passkey: Face ID, Touch ID, Windows Hello or a phone's screen lock instead of a password. Passkeys work on the web workspace and in the app, and the Security page lists every device signed in to your account so you can sign the others out. There's no separate authenticator-app code step.
Every company's records are separated in the database itself, not just hidden in the screens. A manager who also runs a sister company's office, or an owner with two businesses, has one login and switches between companies, seeing each with the role held there.
When you ask TripNerve for help, support staff can open a support session to see your workspace as you do. A banner shows throughout, the session is recorded with a reason, and while it's open nobody can change your name, email, password, passkeys or signed-in devices, or delete your account.
Worked example
A six-person office before the spring season
Mero Himal Treks takes on a second salesperson in November 2026 and wants its new writer to stop publishing blog posts without a check.
| Person | Job | Role | Can't |
|---|---|---|---|
| Ang Dorje Sherpa | Director | Owner | Nothing is off limits |
| Sita Karki | Office manager | Manager | Change roles |
| Rohan Shrestha, Nima Lama | Sales | Sales | Edit trips or crew |
| Anisha Gurung | Operations | Operations | Confirm or cancel bookings |
| Prakash Adhikari | Writer | Content writer (custom) | Publish blog posts or the website |
Sita invites Nima on Sunday 8 November with the Sales role, and the invitation shows on the Team screen until it's accepted. Nima signs up with her Google account from the link, and Sita's phone gets "Nima Lama joined Mero Himal Treks".
Managers can't change roles, so Ang Dorje builds a Content writer role for Prakash: write and edit blog posts, upload photos to the media library, and edit the website's pages, but not publish. Prakash's next post on the Mardi Himal trek waits as a draft until Sita publishes it.
Anisha adds a passkey on her phone, so on the trail she signs in to the app with her fingerprint instead of typing a password.
Common mistakes
Building roles before you need them
Start with the four starter roles and adjust when a real job doesn't fit. Twelve roles for eight people is harder to keep right than four.
Sharing one login
A shared office login means every change looks like the same person made it, and nobody can be removed when they leave. Invite each person.
Giving everyone Manager
Manager can delete trips and bookings. Give sales staff Sales, and build narrower roles where a job needs something in between.
Leaving ex-staff in
Remove people on their last day. Their past work stays recorded under their name.

