Activating and Testing Across Multiple Environments
When testing or activating the platform across multiple environments (for example, staging, testing, or production), you may need to create more than one user account using the same base email address.
This is common when bank or NBFI users want to test the solution from the corporate perspective while already having access to the portal as an administrator.
1. Create the User with an Email Alias
During user creation under the Company Profile, you will need to enter an email alias if your original email address is already associated with another account.
The system does not allow the same email address to be registered twice. To work around this, you can use an alias by adding +text to the local part of the email address.
Example:
Original email:
john@mail.comAlias for testing:
john+customer@mail.com
The platform will treat this as a different user, but all transactional emails will still be delivered to the same inbox (john@mail.com).
2. Receive the Activation Link
After the user has been created, the activation link will be delivered in one of the following ways:
Email notification: If the notification service is enabled in the environment, the activation email will be sent directly to your inbox.
Customer Success team: If the notification service is not enabled in the testing environment, the activation link will be shared with you by the Customer Success (CS) team.
In both cases, you will receive an activation link that allows you to set up the account.
3. Activate the Account
Once you receive the activation link, we recommend pasting it into a different browser or opening it in incognito/private mode. Your regular browser may have cached data or saved history that can sometimes cause errors when loading the activation page.
This workaround is only required for the initial activation. After the account is activated, you will be able to log in normally using the credentials created for that environment.
Best Practices
Use different aliases for each environment or testing scenario.
Keep track of which alias corresponds to each environment.
Save the passwords for each account securely so you can easily access them later.
This approach allows users to activate and test the platform across multiple environments without needing separate email inboxes.