Skip to content
Blog

Travel agency team permissions: who should see what

Tekravel Editorial
Written with the help of AI

The question usually arrives sideways. A new ticketing agent asks why a fare shows one price on the booking screen and another on the report, and you realise she can see the net fare, your markup and the credit balance of every sub-agent you sell to. Nobody decided she should. She was given the same login as everyone else, because setting up anything finer felt like a job for a quieter week.

That quieter week rarely comes, so travel agency team permissions end up decided by default: everybody sees everything, one shared password lives in a notebook by the phone, and the person who left in spring can still sign in. This piece is about deciding it on purpose — which roles an agency actually needs, what should stay out of sight for junior staff, how to cut someone off on the day they leave, and what records you want when a client or a supplier disputes what happened.

Why "everyone sees everything" costs more than it looks

The obvious risk is theft, and it is the least likely one. The common damage is quieter.

An agent who can see your net fare will, sooner or later, quote it — to a friend, to a client who pushes hard, or to the competitor who hires them next year. A staff member who can edit markups will "fix" a price for a client in a hurry and forget to put it back. Someone who can see every office's bookings will answer another branch's client and promise something that branch never agreed to. None of this needs bad intent. It only needs access nobody thought about.

And when something does go wrong — a refund sent to the wrong card, a ticket voided after the deadline, an ADM from the airline for a booking nobody remembers making — a shared login means you cannot say who did it. You pay the ADM, you apologise to the client, and you learn nothing from it. That is the real cost of getting this wrong: not one dramatic loss, but a steady leak of margin and a string of disputes you cannot win because you have no record of who did what.

The roles most agencies actually need

Job titles vary from one agency to the next; the shape of the work does not. Most agencies with a handful to a couple of dozen people on the desk end up with some version of these five roles. Read the table as a starting point to argue with, not a standard.

RoleDoesSeesShould not see or do
Owner / directorSets markups, credit limits and supplier termsEverything, including margins and settlement—
Office supervisorApproves refunds and exceptions, manages the staff of one officeBookings, customers and reports for their own office; markups read-onlyOther offices' clients, supplier contracts, changing credit limits
Reservations / ticketing agentSearches, books, issues, makes changesSelling price, fare rules, the history of their own clientsNet fares, markup rules, sub-agent credit, other offices
AccountsReconciles payments, settlement and invoicesPayments, invoices, credit balancesCreating or changing bookings
Seasonal helpAnswers enquiries, holds bookings for an agent to issueSelling prices and availabilityIssuing, refunds, exporting the customer list

Two rows deserve a second look. Accounts seeing the money but not editing bookings is the separation that catches the most expensive mistakes: the person who records a refund is not the person who triggered it. And the seasonal row exists because almost every agency adds help before Ramadan, Eid or the summer peak — and almost every agency gives that help a full login, because it is quicker.

If you run a single office with three people, you may collapse all of this into two roles: the owner, and everyone else. That is fine. What matters is that the line exists, and that it runs between the selling price and the cost price.

What junior staff should never see

Three things, in order of how much they cost you when they leak.

Net fares and your markup

Your margin is the gap between two numbers, and anyone who sees both knows your business. An agent needs the selling price to quote and the fare rules to explain a change fee. They do not need the net. If your system can only show both or neither, that is a reason to look hard at the system, not a reason to give up on the rule.

Credit limits and balances

If you sell to sub-agents or carry corporate accounts on credit, each account's balance is sensitive in both directions: it tells a staff member which clients are near their limit and which ones are slow to pay. A ticketing agent needs to know whether a booking can be issued on account. They do not need to know how far over the line the account already is.

Other offices' clients

Agencies with two branches — a head office and a counter in a mall, say — tend to share one client list because it is simpler. The cost shows up when one branch's agent leaves with both branches' clients, or when a client is quoted two different prices by two branches on the same afternoon. Each office seeing its own bookings and customers, with the owner and accounts seeing across all of them, is the default worth having.

Offboarding: the same day, not the same month

The day someone leaves is the day their access ends. Not when IT gets round to it — most small agencies have no IT — and not at the end of the notice period if the departure is not a friendly one. Access to a booking system is access to your client list, and the client list is the one thing a departing agent most wants to take with them.

The booking system is the easy part. Everything around it is where access survives. A checklist that works:

  • Deactivate their user in the booking platform and confirm that the next sign-in fails.
  • Change every password that was shared with them: supplier extranets, airline portals, the agency mailbox they used to read.
  • Remove them from the WhatsApp or Telegram groups where clients and suppliers send requests.
  • Reassign their open bookings to a named colleague, so next week's schedule change does not land in an inbox nobody reads.
  • Write down the date and who did each step. You may be asked later.

Deactivate rather than delete where you can. Deleting a user can leave the bookings they made without an owner; deactivating keeps the history attached to a name while stopping the sign-in.

Shared logins make every line of that list harder. If five people used one account, cutting off one of them means changing the password on the other four, which is exactly why it does not get done. Individual accounts are not a nicety here. They are what makes offboarding possible at all.

Audit trails when something is disputed

Disputes in travel follow a pattern. The client says nobody told them the ticket was non-refundable. The airline sends an ADM for a booking issued outside the fare's conditions. A hotel insists the cancellation came after the free-cancellation deadline. Each one is settled by a record, and the record you want answers three questions: who did it, when, and what they saw at that moment.

"Who" and "when" are only possible with individual logins. "What they saw" means keeping the fare rules and the price displayed at the time of booking, not just the final ticket. The notes captured when the booking is made — the subject of our piece on managing travel bookings for clients — are half of this record.

If your system keeps a history of actions per user, find out how long it is kept and whether staff can edit it. If it keeps none, a short note on each booking saying who confirmed the conditions with the client, and how, is the manual version. It is thin, but it is better than nothing when you are answering an airline.

The same split on the client's side

Companies that book through an account with you want the same separation inside their own team: a coordinator who books for everyone, managers who approve, travellers who see only their own trips. If you sell to corporates, that is worth raising when you open the account; our piece on what a corporate travel booking account changes covers that side of it.

Fixing travel agency team permissions in an afternoon

This is not a project. Every tenant on our platform gets its own admin panel with role-based staff permissions, next to its own bookings, customers, markups and reports — so on our side the work is deciding who belongs where, and if you want to map your desk onto those roles before moving anyone, tell us how your team is organised. Whatever system you use, the afternoon looks like this:

  1. List every person who can sign in today, including the ones who have left.
  2. Put each one in a role from the table, and argue about the edge cases now rather than during a dispute.
  3. Close the accounts of the people who left, and give everyone who remains a login of their own.
  4. Sign in as a junior agent and check that net fares and credit balances really are hidden.
  5. Write down who may approve a refund, and put it where the desk can see it.

Step four is the one people skip, and it is the one that matters. Screens often show more than the role names suggest — a margin column on a report, a net price in a booking's detail view. A role called "agent" that still shows the net fare is not a permission. It is a label.

Tekravel Editorial

Travel technology desk

The Tekravel travel-technology desk writes for the trade: agency owners, consolidators and the developers who integrate them. Every article is checked against the platform it describes before it is published.