Employees, roles and the chart your policy runs on
Travel policy by designation only works if the system knows who someone is. Department, job role, manager, and whether the person is still employed, are not decorative fields. They decide which rules apply in search, who must approve a request, and who is allowed to see a trip. When that structure lives in a spreadsheet, policy and approvals drift the first time someone changes role.
GTOS holds employees, roles and the organisation chart in the Client Portal. The chart is the source for approval chains and for access. Rules can be set by designation, department and destination, and matched to your written policy. GTOS is the Global Travel Operating System from Voraal, built on operating experience across 100,000+ trips.
Why the chart is an operating surface
The organisation chart in GTOS is not a picture for an employee directory. It is the structure a travel request approval system reads when it decides who should see a request and whether that person's limit covers the amount. It is also the structure role-based access uses after sign-in, so a traveller, an approver, a finance user and an admin do not see the same workspace.
Policy by designation depends on the same data. A rule that allows a certain cabin, hotel band or advance window for one designation, and a tighter rule for another, cannot run if designation is missing or out of date. See travel policy and the use-case page for policy by department and designation.
Keeping the chart current is therefore a travel-operations task, not only an HR task. When someone changes manager or leaves, the chain and the access should change with them. A programme that reviews the chart when roles change will see fewer requests going to the wrong approver, and fewer people retaining access they should no longer have.
How employee data gets into GTOS
Employee, role and organisation data can be maintained in the Client Portal. Many buyers also ask about a connection from their human resources system. We do not publish a list of certified HRIS connectors, and we do not claim a live, named sync with a particular platform. How employee data will move between your HRIS and GTOS is scoped during implementation and discussed in a demo, against the systems you actually use. See HRIS employee sync.
GTOS is built to scale to 1,000+ employees per client. At that size, a manually reconstructed chart will not stay accurate for long, which is why the organisation structure belongs in the same operating system as policy.
Security around people data
Employee and organisation data is company data. Each company sees only its own records. Access is by role. Two-step sign-in is available on the GTOS app. We do not claim certifications we do not hold. Read Security.
USD is the main currency on this site. Pricing is in USD and available on request.
Frequently asked questions
Do we have to use an HRIS connection to set up the chart?
No. The organisation chart and roles can be maintained in the Client Portal. An HRIS connection, if you want one, is scoped during implementation and is not listed here as a named certified connector.
Does designation really change what a traveller can book?
It can. Policy rules may be set by designation, department and destination, so two people in the same company can see different in-policy options.
Who can edit the organisation chart?
Access is by role. Company admins working in the Client Portal maintain structure. Other roles see what they are allowed to see.
Related
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