Safe automation mode

Review the standing safeguards, audit expectations, and request throttling guidance that apply before Sales Navigator extraction workflows are scaled beyond a single run.

Standard batches

Up to 500 leads

Balanced pacing is the default for routine approved prospecting exports.

Expanded reviews

501–2,000 leads

Confirm segmentation and use Careful pacing unless the request has explicit acceleration approval.

Scale approvals

2,000+ leads

Split into smaller audiences and capture written approval before scheduling repeated runs.

Standing control set

Compliance operating checklist

A static route-level checklist for the controls every Sales Nav workflow should satisfy before scaling.

Controls active6/6

Approved business purpose documentedEvery extraction must map to an active campaign, customer request, or enrichment workflow.

Search scope reviewed before launchAudience filters, geography, and lead volume should be intentionally bounded before a run starts.

Source authorization confirmedOperators are expected to use only accounts, lists, and records they are authorized to access.

Audit trail retainedCapture operator, timestamp, source URL, requested size, export file name, and delivery option.

Rate-limited pacing selectedUse Balanced or Careful pacing for broad searches and reserve Fast for small, approved batches.

Export handling controls understoodDownloaded files must remain in approved storage and follow retention, sharing, and deletion rules.

Scaling note

General compliance guidance lives here; the new-run setup screen now keeps only run-specific launch readiness checks.

Controlled request intake

Run only scoped Sales Navigator people or account searches that have a clear owner, approved purpose, and expected audience size.

Account-safe pacing

Prefer smaller batches, avoid repeated identical searches, and choose conservative priority when a search expands beyond a narrow segment.

Export stewardship

Treat exported records as controlled data: store them in approved destinations, avoid ad-hoc sharing, and retain only what the workflow requires.

Audit expectations

Evidence required for every workflow

Audit evidence should make each run explainable, repeatable, and easy to review if a campaign owner or compliance stakeholder asks for details.

Operator identity, request timestamp, and service option are recorded with each submitted run.

Source URL, Request Unique ID, lead volume, and file name must be reproducible from the run record.

Exceptions, webhook failures, retries, and manual restarts should be noted before a second attempt.

Campaign owners should be able to explain why each audience was selected and how the export will be used.