Organizations often want to create what is known informally as a "one-way" territory gateway, meaning that they want documents to flow only in one direction. For example, a territory that handles employee-related documents might want to broadcast certain documents to, but never receive documents from, a territory that handles customer support documents.

To create this type of territory gateway, you must create a complete gateway connection (that is, you must create and configure both gateways in the gateway pair). Creating a one-way territory gateway does not mean that you create only one side of a territory gateway connection. To achieve the "one-way" nature of this type of connection, you must configure the permission settings on each territory gateway to restrict the flow of documents to one direction.

For example, if you want to limit the flow of documents from the employee territory (EMP) to the customer support territory (CUST), you would set permissions as follows:

On gateway EMP>CUST:

On gateway CUST>EMP: