Features

Each company sees only its own travel data

Multi-tenant travel software security is a question every company should ask before it puts policy, passports and card-related travel data on a shared platform. The first answer that has to be clear is boundary: each company must see only its own records. Everything else — roles, two-step sign-in, an audit trail — sits inside that boundary.

GTOS is built around per-client data separation. A company working in the Client Portal, its travellers in My Mobility, and the desk working on that account in Control Tower, are looking at that company's trips. They are not looking at another client's programme. GTOS is the Global Travel Operating System from Voraal, built on operating experience across 100,000+ trips.

What "per-client" means in practice

Separation is not only a login wall. It is the rule that bookings, approvals, spend, documents and organisation data belong to one company and are not visible to another. Agencies and travel management companies may operate more than one client on the same platform. That is exactly why the boundary has to be strict. A desk user should be able to service an account without crossing into a different client's file.

Inside a company, role-based access then limits what each person can see or change. Separation between companies, and access within a company, are different layers. Both are required.

We describe this model honestly. We do not claim ISO, SOC or similar certifications we do not hold. We do not invent penetration-test scores or hosting badges. For the questions to ask any vendor, including us, see security questions and the Security page.

How this relates to sign-in and the audit trail

Sign-in for the product lives at app.mygtos.com, separate from this marketing site. Two-step sign-in is available on the GTOS app, so access is not only a password. After sign-in, the user is still inside one company's data, with a role.

The audit trail records requests, approvals and changes inside that same boundary. A review of one company's programme should not require access to another company's data, and a trail should not leak across clients.

For companies and for the agencies that serve them

If you run your own programme, separation means your travellers and your finance team are not sharing a workspace with another organisation. If you are an agency or a TMC running more than one account, separation is what makes that model tenable. GTOS is built to scale to 1,000+ employees per client, and to hold many clients on the platform without mixing their records.

USD is the main currency on this site. Pricing is in USD and available on request. Conversations about how a particular programme is set up, including how an agency desk is granted access to more than one client, belong in a demo rather than in a generic access claim on this page.

Frequently asked questions

Can one company user ever see another company's trips?

Each company sees only its own data. That boundary is the starting point of the security model.

How do agencies work across more than one client?

The desk can service each account in Control Tower, inside that client's record. Per-client separation still applies. A demo can walk through how that looks in practice.

Do you publish security certifications here?

No. We describe controls we actually operate: per-client separation, access by role, two-step sign-in and an audit trail. We do not claim certifications we do not hold.

Now taking early-access requests

See GTOS in a demo

We are now taking early-access requests. Demo accounts are available now.

  • A walkthrough of the Client Portal, My Mobility and Control Tower
  • Your travel policy, set up in a demo account
  • USD pricing discussed on request, with PKR quotes available

Prefer email or WhatsApp? insights@goglobal.pk · +92 320 4111222

Request a demo

We will reply by email to arrange a time.

By submitting, you agree to our Privacy Policy and Terms of Use.