Identity and sign-on, scoped honestly

GTOS takes a narrower, honest position. 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 today, so access is not only a password. After sign-in, role-based access decides what each person can see, inside per-client data separation. Single sign-on with a company's identity provider is a conversation we will have in a demo and scope during implementation. We do not publish a list of named providers or certified SSO connectors on this page.

GTOS is the Global Travel Operating System from Voraal, built on operating experience across 100,000+ trips.

What is already in place

Before any identity-provider discussion, the access model has to be solid. Two-step sign-in, role-based access, an audit trail of requests, approvals and changes, and a clear boundary between companies are the controls we describe because they are part of the product. They are also the controls a security reviewer should look at first. See Security and security questions.

We do not claim ISO, SOC or similar certifications we do not hold. We do not invent identity-protocol badges.

How an SSO conversation is scoped

If your company requires single sign-on, bring the identity setup you actually use to a demo. We will talk about what can be connected, what would be configured during implementation, and what is not available. The related integrations page, SSO and identity providers, follows the same rule: no named connectors, no implied certification.

That discipline exists because travel systems hold itineraries, organisation data and, in many programmes, document details. An over-stated identity claim is worse than a clear "this is scoped in implementation."

What SSO does not replace

Even when single sign-on is in place in a programme, it does not replace role-based access, and it does not replace two-step sign-in where your security team still requires a second factor. It also does not cross the company boundary. A successful sign-on still lands a user inside their own company's data.

USD is the main currency on this site. Pricing is in USD and available on request. GTOS is built to scale to 1,000+ employees per client, which is often the size at which SSO becomes a formal requirement rather than a preference. Bring your identity requirements to the walkthrough so the conversation stays attached to what can actually be configured.