Running Mass Transfer Approval Requests safely involves precise filtering, preview verification, and follow-up communication with the new approver. The steps below cover the standard flow.
- Confirm the scenario
Verify this is a one-time reassignment rather than an ongoing coverage need. For ongoing, use Delegate User instead.
- Identify the source and target
Confirm which user has the pending requests (source) and which user should receive them (target). Confirm the target has the appropriate access to act on the requests.
- Open Mass Transfer Approval Requests
Setup > Data > Mass Transfer Approval Requests. The page is straightforward; pick the source user.
- Set additional filters
Optionally filter by approval process, date range, or submitter. The narrower the filter, the safer the operation.
- Preview matching requests
Click Find. Review the count and sample. Confirm everything matches expectations before proceeding.
- Select target approver
Pick the new approver. Confirm they have access to the relevant records and the approval process.
- Execute and notify
Run the transfer. Send a separate communication to the new approver letting them know they have inherited pending requests and the context.
Pick the user whose pending requests will move.
Optional narrowing to one specific process.
Optional narrowing by submission date.
Optional narrowing by who submitted.
The user receiving the reassigned requests.
- Only pending requests can be reassigned. Completed approvals are fixed; the audit history cannot be rewritten.
- Broad filters risk reassigning to inappropriate users. Verify the preview before executing.
- Reassignment is reversible only by repeating in the opposite direction. Build the filter carefully the first time.
- The new approver receives standard notifications. Pair with manual communication explaining the context.
- For ongoing coverage, Delegate User is the proper tool. Mass Transfer is for event-driven one-time changes.