As Proof usage grows, administrators may find that certain configurations are desirable for subsets of users, but not for everyone.
For example - suppose the Department of Highways and Public Works has divisions related to transportation (e.g. regulation) and another related to capital projects. Each have very different workflow that they route through Proof, but each share the same Deputy Minister as final approver for many matters.
This kind of usage is a great candidate for applying the Proof concept of units to give each business unit distinct control of how routings are configured.
All settings that concern routings - the range of routing types, the range of step actions, what templates apply to routing types, as well as what users can administrate the routing - are associated with the routing’s unit. The term unit is in reference to business unit; this feature is designed and most effective for business units that need to tailor their operations in ways that may not be appropriate for the entire department.
Units are always in operation in the Proof system, but are kept in the background until multiple units are in operation. Specifically, every routing is associated with a unit, but units only become prominent in the UI when multiple units exist in a tenant, and only for users that can create routings in more than one unit.
Units must be created by tenant administrators, but can subsequently be administrated by appointed users. To create a unit, administrators must go to
When creating a unit, administrators can choose in which document library the attachments are located. This is appropriate for groups using distinct sharepoint automations.
Users can have one of three relationships to a unit
Unit administrators will be able to