Approval Setup – Xebra allows for the creation of an approval hierarchy. You may have as many levels of required approval as needed. For instance, a general staff member of a bank might be able to place an order, which must be approved by their branch manager. Once approved by the branch manager, that same order can be directed to a regional manager for approval and then even on further to a corporate controller. Along the way, each approval operator has the ability to make changes or delete the job as well as approving it. Only once the highest approval operator in the hierarchy has approved the order does the order come to the distributor for processing.
Approval Operator – This would be an operator that has the ability to approve orders at some level. An operator may be set as an approval operator but still require approval. This just means that they are a middle level approval operator within a much larger hierarchy.
For orders pending approval at levels below this web user in the approval hierarchy – Used alone, only when a multi-level hierarchy is in place.
Allow Viewing – When checked, this web user has the ability to view any orders pending approval at or below their level within the hierarchy.
Allow Edit/Delete/Approval – When checked, this web user will have the ability to edit, delete, or approve any orders at or below their level within the hierarchy.
For ANY orders pending approval regardless of the approval hierarchy – For single level hierarchies, all approval operators will require these settings. For multi-level hierarchies, only those approval operators at the very top should have these options checked.
Allow Viewing – When checked, this web user has the ability to view ANY orders pending approval.
Allow Edit/Delete/Approval – When checked, this web user will have the ability to edit, delete, or approve ANY orders.
Web User set as the Approval Operator; sample setup
Web User requiring Approval; sample setup