Overview
Access to TripBuilder in a B2B setting (such as planning and booking itineraries, customer care operations, product management, and system administration) requires user authentication. This article explains how to log in to TripBuilder.
TripBuilder Log In
After signing up for TripBuilder, Nezasa will create an initial administrator account. This account allows you to manage the platform and create additional accounts with various user roles.
First User Log In
When a new user account is created, a welcome email will be sent with a link to set a new password.
Note: If the welcome or set-password email does not arrive, check your spam or junk folder and confirm with your TripBuilder administrator that the user was created with the correct email address. If you are already logged in to a different TripBuilder account or session, log out first. When session confusion is possible, use a private or incognito browser window to open the link or continue the login flow.
In the email, click the Set Your Password button. A new browser window will open for you to create your password.
Note: When an administrator creates a new TripBuilder account, no password, not even a temporary one, is generated or defined.
Once a password has been set, the user is automatically logged into TripBuilder. The TripBuilder Dashboard will then appear, showing the areas accessible based on the user roles.
Standard User Log In
To log in to your TripBuilder instance, enter the URL in your Internet browser.
The production URL format typically follows: my-id.tripbuilder.app
Replace my-id with your setup ID.
Know more: If your production domain has been white-labelled, it will follow a different pattern. For more information, see the article How to white-label / mask my domain.
Important: Start account actions such as login and password reset from the correct TripBuilder instance URL. If your organisation uses a white-labelled portal domain, use that white-labelled URL instead of a different TripBuilder URL. Email links and redirects are tied to the relevant instance and domain configuration.
At this point, the TripBuilder login screen will be displayed.
Note: To ensure the security of TripBuilder and protect your valuable data, our session management practices adhere to leading security standards, including OWASP best practices. Our goal is to provide a secure platform with minimal disruption to your daily activities:
Absolute Session Timeout is set to 12 hours.
Idle Session Timeout is set to 12 hours.
In the near future, we plan to gradually tighten these settings to enhance security even further.
FAQ
Q: What should I do if I forget the URL for my TripBuilder instance?
A: Follow these steps:
Go to https://app.nezasa.com/
Enter your Company ID and click the Continue button. If the Company ID is valid, you will be directed to the appropriate login page for your TripBuilder instance
Q: What should I do if I forget both the URL and Company ID for my TripBuilder instance?
A: Follow these steps:
Go to https://app.nezasa.com/
Click the link Forgot your company ID?
Enter your email address and click the Continue button
You will receive a list of all the company IDs and URLs associated with your email address.
Note: If the company ID recovery message does not arrive, check your spam or junk folder and confirm that the email address you entered is the one associated with your TripBuilder access. If no email arrives, ask your organisation's TripBuilder administrator to confirm that your user account is active and associated with the correct company.
Q: What should I do if I forget the user password for my TripBuilder instance?
A: Refer to the article How to reset my password?
Q: What should I do if TripBuilder account emails still do not arrive?
A: If welcome emails, password reset links, or company ID recovery messages do not arrive after you check spam or junk folders and use the correct TripBuilder instance URL, your organisation's IT or domain administrator should review email filtering or quarantine settings and sender authentication or delivery configuration. For sender authentication details, see How to white-label / mask the FROM email address?