Electronic signatures > Configuring electronic signatures

Signature policies

Signature policies define the module parameters and fields that will require a signature before an operator can write to it, the type of signature required, and the default signature requirement for the module parameters and fields not listed in the signature policy. The signature requirement options are Comment Only, Confirm, Confirm and Verify, and None.

Note

The signature policy for Field Confirmation takes precedence over the policy for Parameter Confirmation even if the Field Confirmation requirement is less stringent than the Parameter Confirmation requirement.

Figure: Properties page for configuring parameter confirmation requirements

Signature policies can be renamed and deleted from the database. They are subject to Version Control if Version Control is enabled. Policies can be printed and database objects that have a relationship with the policy (References) can be requested for them.

Signature policies are under the Electronic Signatures container in the DeltaV Explorer.