Overview
TripBuilder administrators managing complex setups with multiple Distribution Channels (DCs) can use the Link User to a Distribution Channel feature to control or restrict user access per DC. By default, this feature is disabled when a new user is created, meaning that access to all DCs is the default behaviour.
How to Link a User to a Distribution Channel
Follow these steps to ensure that your team has the appropriate level of access within the TripBuilder application:
When creating or updating a TripBuilder user, search for the Link User to Distribution Channel checkbox.
Know more:The article How to Create a New TripBuilder User? provides a detailed walkthrough on user creation.
Enable the Link User to Distribution Channel option.
A new field will be displayed where you can specify which DCs the user can access. If no DCs are selected (i.e., the field is empty), the user will have access to all DCs.
To remove access to a distribution channel, click the "X" next to it.
To add access to a DC that is not yet available to the user, click on the field. A drop-down list of all available DCs in the TripBuilder instance will appear.
Click the Save button once the DC assignments are complete.
Please note:
If this feature is used during user creation, the new user will receive an email to set their password. If DC restrictions are applied, the access URL for setting the password will follow these rules:
If the user only has access to one DC, the URL will point to that one
If the user has access to more than one DC, or if no restriction is imposed, TripBuilder will choose the first DC the user can access.
For more information, refer to the article How to Log In to Your TripBuilder Instance.
Which TripBuilder Data is Restricted?
For demonstration, let's consider a TripBuilder instance with three DCs:
RubyTravel-B2B-DE (German B2B market)
RubyTravel-B2B-CH
RubyTravel-B2C-CH
If a user is restricted to access only the RubyTravel-B2B-DE DC, access to data is restricted as follows:
Itineraries in Customer Care
The Itineraries page will only display itineraries from the RubyTravel-B2B-DE DC in the Distribution Channel column.
Itineraries from RubyTravel-B2B-CH and RubyTravel-B2C-CH DCs will not be displayed.
Resold itineraries will be displayed with the reseller entity’s DC indicated, if applicable. In the example this is represented by the funtravels DC.
Know more:
Additional information about P2P setups can be found in the Peer to Peer Reselling Support article.
Components in Customer Care
The Components page will follow the same access logic as the Itineraries page, displaying components only from the RubyTravel-B2B-DE DC or resold DCs.
Group Tours
In Group Tours, only itineraries created within the RubyTravel-B2B-DE DC will be listed under the group tour departure dates.
This restriction is also visible in the itinerary details Overview section...
... and in Pax Details, where only travellers from accessible DCs will be shown.
Itinerary Report
The Itinerary Report respects user restrictions on DCs, that affect data visibility.
Know more:
Additional information on how to request an Itinerary Report can be found in the dedicated article.
Regardless of the navigation path used to request the report, the same Request Itinerary Report modal is present.
In the Distribution Channel Filter field, only the RubyTravel-B2B-DE option is available for user selection. The value in Number of itineraries will align with the existing DC restrictions.
For the restricted user in our example, having no value for Distribution Channel Filter or selecting RubyTravel-B2B-DE will result in the same number of itineraries.
When a report request is triggered, a CSV with the exported data is sent to the defined email. When viewing the data in a standard spreadsheet, the Distribution Channel column only contains references to RubyTravel-B2B-DE and funtravels (for resold itineraries) DCs.