The Application Server provides the possibility for users to approve the data of features and observations this of course also includes the possibility to deny approval of features or observations.

Approval processes in Redbex are user definable multi-user, multi-stage processes, that are instantiated for features or a set of observations belonging to a feature with the aim to approve or deny the data of features or observations. Features or observations for which an approval process has been started are protected against data modification.

Running approval processes are called Approval workflows in Redbex; they are created based on approval templates. Each workflow can be used to approve or deny a single feature or a set of observations belonging to the same feature. Approval workflows cannot be started for calculated features.

Approvals are meant to be the pendant to signatures on printed reports, but you have to decide yourself if the approvals you do within Redbex are in any way legally binding. Depending on the approval process security defined through the approval template, different security levels can be reached.