E-Signature and Audit Trail

When to read this

A task prompts e-signature; you need who changed what when; or you reconcile side-effect creates in audit. PDF signature pages may render separately from signature child records.

When e-signature appears

Typically all configured:

1. Parent object eSignatures enabled.
2. Workflow step prompts for e-signature.
3. You complete the step in My Tasks as assignee.

Enable alone does not sign—workflow must require it.

Signing during task completion

1. After approve/reject (when configured), enter signature flow.
2. Step-up authentication per policy.
3. Pick Capacity (role meaning).
4. Confirm Meaning text when shown.
5. Platform writes read-only signature child and audit event.

Signatures are not user-editable afterward; corrections follow vault procedure.

Where to read signatures

Inactive parent state may block signed task completion—check lifecycle.

What object audit captures

How business users view audit

1. Audit trail on record detail (needs permission).
2. Filter by time, user, action, field.
3. Vault may offer export via bulk actions (retention varies).

No change, no row: save without real field change often skips edit audit.

On Behalf Of

For compliance, read On Behalf Of when User is System.

Document activity vs object audit

Document view/download/bump may log document activity; field changes may also hit object audit. Admin system logs are separate from record audit.

FAQ

Next

• When tasks prompt sign → My tasks
• Forbidden / no audit → Security basics