3rd Party Access to your Warehouse

3rd Party Access to your Warehouse Instance with an entity that already has an Opendock Warehouse or Carrier Login Account

As a new Opendock customer, you may want/need to give your 3PL’s, Brokerages, or Carriers access to view/edit your Warehouse Schedule.
This is entirely different from the Carrier Instance in which these entities can book appointments against your availability.
This is to be a warehouse “user” in some capacity in conjunction with yourselves as the customer. You decide their user permissions.
This could be an issue, especially if your 3PL/Broker/Carrier also has access to other Opendock Warehouse Instances.
The issue stems from the fact that a unique email address used for warehouse login can only be used for one warehouse organization unless the user is deleted.
In addition, a 3rd party accessing, monitoring, or editing Warehouse Schedules on your behalf, will prefer to have any and all updates/notifications be directed to the same email inbox they are already using for other Opendock Warehouse Customers.

A unique email address will be required to log into each individual warehouse org instance, however most modern email service providers have options for adding unique emails to be redirected to your inbox, or manipulating your email address in a unique way to do the same.
Microsoft Outlook Instructions here.
Google Mail Instructions here.
For most modern email providers, you can simply add a “+” character with a unique

string of characters after the main address right before the “@” sign.
Example:
- john.doe@gmail.com might already be used to log into Customer A’s Warehouse Instance.
- John Doe could be signed up as a user for Customer B’s Warehouse Instance by signing up with the email address john.doe+customerB@gmail.com
- In this scenario, any automated email notifications from both customer A & customer B would be directed to the same inbox.
- This example is endless, as you could add customer C & D etc.
It is important to check with IT and Network Security teams to see if this possible within

your organization.
We prioritize customer privacy, and will not allow a unique email login to access any data

that is not owned by the customer that invited you to be a user in their instance.