Use Signatures to configure how a step is signed and who is eligible for its requirements. A signature requirement's name is a label; it is not a user or role assignment.
Read-only example. These controls are disabled in the capture; use an editable practice draft to configure them.
Enable electronic signing
Select the step and open Signatures.
Under Sign Settings, turn on Electronic Signature when the step should request electronic signing.
Inspect the existing required signatures before adding more. A default requirement may already be present.
The default requirement cannot be renamed or deleted through the same controls as an added requirement.
Add another requirement
Enter a name, such as Quality review, in the new-requirement field.
Click Add Signature.
Select the applicable Certifications for that requirement, if eligibility must be restricted.
Repeat only for genuinely separate required signatures.
There is no role/user dropdown in this configuration and no Require all signers switch. Do not type Supervisor as a name and assume that it restricts signing to supervisors.
Before relying on certification restrictions, confirm the intended users have the appropriate valid certifications.
Control multiple signatures
Enforce Sequence Order controls whether requirements must be signed in the configured order.
Allow Signature by Same User controls whether the same user can sign multiple requirements. Turn it off when the process needs different people, then test with the intended users.
For an operator-plus-reviewer process, inspect the existing operator/default requirement, add a Quality review requirement, configure the reviewer's certification, and choose sequence and same-user behavior deliberately.
Configure unsigning separately
Use Unsign Settings for the requirements to reverse an existing signature. Signing requirements do not automatically express your cancellation policy.
If only certified reviewers should cancel completion, configure the appropriate certification in the unsigning requirements and test that case.
Test the result
Use Preview to inspect the step, then a controlled real test session to verify:
An eligible user can sign.
A user without the required certification cannot satisfy that requirement.
Multiple requirements follow the intended order.
Same-user signing behaves as intended.
Cancelling a signature follows Unsign Settings.
Review the recorded identity and time in the resulting session record. Publish only after the intended cases pass.