Approvals V5 — Bulk approver reassignment & download restriction (backend)

What this skill covers

Problem class: The customer (or CSM) updates approval configuration on a workspace workflow, but contracts already in progress still have pending approvals with the old approver mapping, old restrict-action behavior, or both. They need data fixes on existing approval rows, not only the live workflow template.

Typical symptoms

• Pending approvals still show the previous approver after the workflow was republished or approvers were edited in Workflow Manager.
• Support asks whether reassignment can be done in bulk from the UI; only a handful of approvals may be affected, but UI/workflows are workflow-definition oriented—investigators confirmed confusion between workflow-level setup and per-contract approval instances (#incident-20260319-high-crunchbase-request-to-update-approver-and-permissions-for).
• Customer wants a specific user to download while approvals are in progress, under Restrict Actions → Download—requires aligning ApprovalV5RestrictAction and related restriction ApprovalV5ActorMapping rows.

Product / safety note: Engineering may flag that bulk backend changes are not first-class product features and can have unwanted side effects—get explicit scope (approval names, workflows, date cutoffs, which contracts) and dry-run before write paths. See escalation below.

When to use / not use