The running user is set while you define a reporting snapshot in Setup. You assign it once, and it governs every scheduled run until edited. Choose the account before scheduling, since the snapshot reads the source report as that user.
- Open the Reporting Snapshots page
From Setup, type Reporting Snapshots in the Quick Find box and select Reporting Snapshots. Click New Reporting Snapshot, or open an existing one and click Edit.
- Select the running user
In the Running User field, click the lookup icon and pick an active user whose data visibility matches what the snapshot should capture. Only users with Modify All Data can choose a running user other than themselves.
- Confirm the account's access
Verify the running user has Run Reports, Create on the target object, and access to the folder that holds the source report. Add Customize Application if the target object is still In Development.
- Map fields and schedule
Map each required target field to a source report field, then schedule the snapshot to run daily, weekly, or monthly at a preferred start time in your time zone.
- Monitor the run history
After the first scheduled run, open the snapshot and check the Run History section to confirm it succeeded. Optionally add internal users to the completion email so failures surface quickly.
The user whose access governs the source report when the snapshot runs; their visibility defines the captured rows and bypasses sharing on the target.
A tabular or summary report, in a folder the running user can open, whose results are saved into the target object.
The custom object that receives the snapshot rows; required fields must be mapped and it cannot exceed 100 custom fields.
Daily, weekly, or monthly, with a preferred start time in the scheduler's time zone; the run happens within an hour of that time.
- Captured rows bypass sharing: anyone who can read the target records sees the running user's view, even data they could not otherwise access.
- A deactivated running user makes the snapshot fail; deactivating the account silently breaks future runs.
- The running user must have folder access to the source report, not just the Run Reports permission.
- Each run caps at 2,000 new records; a broad running user can exceed it and lose the extra rows, so filter the source report.