Specifically for consignee and consignor access, you can now determine whether cargo items that have both the consignee and consignor in the same data access group, or whether only one of the consignee or consignor needs to be part of the access group for the user to see the cargo data. Examples each scenario are below.
There is a new system configuration “Must Have Data Access For Both Consignee and Consignor” in System Config under the Defaults tab.
With the new system configuration selected, user Exporter is a Consignee who has access to data using the Consignee/Consignor Data Access Group ‘FWD’.
The user is also part of the ‘Shippers’ organisation which also has consignee data access for group ‘FWD’.
Add the consignees and consignors to the FWD group user Exporter can view the cargo for.
This means only cargo items that have both the consignee and consignor set with one of these three options, will be viewable by user Exporter.
The existing ‘Include if not is set’ option shown above is also not selected to ensure only those in the data access group can see the data, rather than cargo where the consignee and the consignor are blank.
Put into practice, there are 3 containers, all ISO Type 22RT on site;
- TEMP05000; where the Consignee is ABCMN and the Consignor is RCHFC.
- TEMP05001; where the Consignor is RCHFC and Consignee is blank.
- TEMP05002; where the Consignee is TSC and Consignor is MMET.
If the new system configuration “Must Have Data Access For Both Consignee and Consignor” is not selected, user Exporter can see all cargo where at least one of the consignees or consignors is in the data access group. i.e. All three containers in this example.