In the interest of documentation: As of this writing, the implementation mentioned above covers cases where an org unit and all children of it should be considered a common endpoint for transit purposes, but with the ability to limit that to non-hold transits or hold transits only where applicable. That is, any transit that would end at an org unit within the suppression range would either be completed (if from outside the range) or never even started (if from within the range). It does not offer automatic configuration of this based on depth in the org tree, but rather requires one or two settings to be set at each org unit you wish to use the feature for. This allows it to be more flexible with complex options. It can also be overridden at any level of the tree by applying the setting there. For an example, assuming the following org tree: Consortium -System A --Library 1 ---Department 1 ---Department 2 --Library 2 ---Department 3 ---Department 4 -System B --Library 3 ---Department 5 ---Department 6 ---Bookmobile 1 --Library 4 ---Department 7 ---Department 8 ---Sub-library 1 ----Department 9 ----Department 10 System A's libraries are actually both in the same building but split for policy reasons, and thus does not want re-shelving transits to occur. Thus, "Suppress Non-Hold Transits" is enabled for System A. Transits for holds will still be generated, to direct them to the correct hold shelf. Each of the two libraries in System A has only one hold shelf, however, shared by all departments within. So applying "Suppress Hold Transits" at Library 1 and Library 2 will prevent holds from generating transits between departments and the main libraries, but holds will still generate transits between the two libraries. System B's libraries are two different buildings, so System B has no settings applied at it, as transits should happen between the libraries. Library 3 has one hold shelf and wants re-shelving to happen without transits, so both settings are applied at it. Thus, Library 3 will not generate any transits within itself. However, Library 3 has a bookmobile, and items should transit in and out of it. So both settings are applied to the bookmobile with the value set to "false" to disable transit suppression for the bookmobile. Library 4 has the same basic setup as Library 3, but has a specialist sub-library within it, with hours differing from the main library. Due to this Library 4 wants items to transit to and from the sub library, but not within it. By setting both settings at the sub-library it becomes a transit suppression group of its own, suppressing transits within itself but not between it and Library 4. Thus, from a settings point of view, the above can be set as follows, with T representing non-hold transits, H representing hold transits, + representing a true value, and - representing a false value: Consortium -System A (T+) --Library 1 (H+) ---Department 1 ---Department 2 --Library 2 (H+) ---Department 3 ---Department 4 -System B --Library 3 (T+) (H+) ---Department 5 ---Department 6 ---Bookmobile 1 (T-) (H-) --Library 4 (T+) (H+) ---Department 7 ---Department 8 ---Sub-library 1 (T+) (T+) ----Department 9 ----Department 10