Travel that follows your people lifecycle.
SCIM auto-provisioning from your IdP. SSO with Okta, Azure AD, Google Workspace. Role-based access that mirrors your org chart. Graceful offboarding that revokes platform access and reclaims credit balances. Travel onboarding measured in minutes, not weeks.
Travel onboarding shouldn't slow your hiring pipeline.
Most enterprise travel platforms still require manual onboarding. HR adds the new hire to the HRIS. Travel manager creates the profile in the travel platform. Finance assigns a card. Three systems, three forms, three approvals. New hires wait 5–10 days before they can book a trip — long after their first day.
Offboarding is worse. When someone leaves, who reclaims their unused flight credits? Who removes their access? Who cancels in-flight bookings? Most companies have no defined process. Credits sit unused and expire. Departing employees retain platform access for weeks.
Travel Code provisions and de-provisions through SCIM 2.0 with your IdP. New hire shows up in your HRIS — travel access ready in seconds, not days. Off-boarded employee — credits reclaimed, access revoked, in-flight bookings flagged for review. Travel ops follows people ops, automatically.
Typical travel onboarding lag from start date to first booking on legacy platforms.
Average unused flight credit value at offboarding when reclaim isn't automated.
Average platform-access retention for offboarded employees without SCIM.
Travel that mirrors your org.
SCIM 2.0 auto-provisioning.
Real-time SCIM 2.0 sync with Okta, Azure AD, Google Workspace, JumpCloud, OneLogin, and any standard SCIM endpoint. New users provisioned automatically with role mapping. Group memberships drive policy assignment. Average provisioning latency: 3.6s p95.
SSO with your IdP.
SAML 2.0 and OIDC supported. Single-sign-on from your IdP — same login experience as the rest of your stack. Conditional access policies (MFA, device, network) enforced at IdP layer. No separate Travel Code passwords for users to manage or forget.
Role-based access control.
Five default role tiers (Traveler / Manager / Admin / Finance / Owner) plus custom roles. Map IdP groups → role + policy + GL coding automatically. Department changes, promotions, transfers all flow through. No manual role updates.
Graceful offboarding.
Off-boarding flow runs automatically when IdP marks user inactive: platform access revoked, in-flight bookings flagged for the manager, expense submissions auto-finalized, credit balances reclaimed and re-attributed to the company. Audit log retained per your retention policy.
Day 1 to last day, no HR intervention.
When a new hire joins, travel access is ready before their first standup. When someone changes roles, policy follows. When they leave, access closes and credits return. All from your IdP, no manual steps.
Provisioned in seconds.
HRIS adds new hire → IdP propagates → SCIM event triggers Travel Code provisioning. Profile created with role, department, manager, GL coding inherited from IdP attributes.
Role changes follow promotions.
When someone changes role or department, IdP group membership updates → Travel Code policy updates within seconds. New approver assigned. New OOP thresholds applied. No manual reconfiguration.
Access revoked, credits reclaimed.
IdP marks user inactive → Travel Code: revokes platform access, flags in-flight bookings for manager review, finalizes pending expense submissions, reclaims unused flight credits.
Audit trail retained.
Audit log retained per your data retention policy (default: 7 years). Configurable per-region for GDPR or sector-specific compliance. Full event history exportable per user, per booking, per transaction.
Common HR & Ops questions.
Which IdPs do you support?
Native SCIM 2.0 connectors for Okta, Azure AD (Microsoft Entra ID), Google Workspace, JumpCloud, and OneLogin. Generic SCIM 2.0 endpoint available for custom IdPs. SAML 2.0 and OIDC supported for SSO. Setup typically 30–60 minutes with your IT team.
How does role mapping work between IdP groups and Travel Code?
You map IdP groups to Travel Code roles and policies in admin settings. Common patterns: department groups → policy assignment; seniority groups → OOP threshold; cost-center attributes → GL coding. Mappings can be updated without code changes.
What happens to in-flight bookings when someone is off-boarded?
Bookings within 30 days of departure are flagged for the manager with three options: cancel and refund, transfer to another employee (where carrier rules permit), or convert to credit. Bookings beyond 30 days follow company-configured policy. The audit log captures every disposition decision.
How are credits reclaimed at offboarding?
Unused flight credits with the offboarded employee's name are flagged. Where carrier rules permit transfer (most US domestic carriers, some Lufthansa fares), credits are reattributed to the company pool. Where rules don't permit transfer, credits are tracked and used for the next booking under the same employee name within the credit's validity period.
See provisioning, by your IdP.
30-min demo with your IT team — bring your IdP and we'll set up SCIM live during the call.