← Evidence
WINROVE / EVIDENCE / BROWSER COMPANION

Capture a public notice you already have open.

The companion files a public notice from a tab you already have open. Allowed origins today are sam.gov and acquisition.gov. Login-walled aggregators are not on the allowlist. For BidSearch-class exports, use Pursuits → Import.

Open Evidence records ↗

What this is not

Boundaries from the customer guide, stated on the record.

  • Passwords, cookies, form fills, headers, or unrelated page content.
  • Reuse of your SAM.gov or aggregator login session.
  • Scraping subscription portals. Use Pursuits → Import for entitled PDFs and CSVs.
  • A store listing claimed as public if it is not yet available to you.

Keep the scope visible.

Task views describe the same workflow the workspace exposes. Availability is confirmed per organization.

Read the scope

Operation availability

Evidence: Record provenance, permitted sharing and revocation

Existing records · In development

A shared view does not transfer ownership or expose personal records.

Ask about access
INSIDE THE WORKFLOW

See the work in detail.

Choose a task to understand the records, decisions and next step.

Review what a connection may read or change

Inspect the provider, permitted operation, data direction and organization authorization. OAuth, webhooks, directory provisioning and developer controls each need verified configuration.

What you leave with: A connection scope with visible limits.

Availability is confirmed per organization before this operation is enabled.

Keep account and workspace access clear

Sign in, verify, select a workspace and return to the original task. Memberships, capability access and record grants remain separate, including when a session or invitation is revoked.

What you leave with: The correct account in the correct workspace.

Availability is confirmed per organization before this operation is enabled.

Review access, billing and account lifecycle

Inspect the capability request, current entitlement and responsible billing contact. Export and account closure preserve required retention and organization responsibilities.

What you leave with: A scoped account request with a clear next step.

Availability is confirmed per organization before this operation is enabled.

Receive the right action for the event

Keep message events, intended recipients and record destinations together. Security and required workflow notices differ from optional preferences; an email preview does not establish live delivery.

What you leave with: A message action that leads to the correct task or safe explanation.

Availability is confirmed per organization before this operation is enabled.

Carry reviewed evidence into the next workflow

Name the source record, recipient, purpose and version in a handoff. Recheck the grant at the destination and preserve history when access changes.

What you leave with: A traceable handoff without silently copying private work.

Availability is confirmed per organization before this operation is enabled.

Understand service continuity and data recovery

Source freshness, job state and recovery receipts explain whether work is pending, uncertain, failed or confirmed. Organization operators manage these controls within their authority.

What you leave with: A visible status and a safe recovery path.

Availability is confirmed per organization before this operation is enabled.

Know when AI may assist

Review the allowed operation, source context, budget and human responsibility before assistance runs. AI authority and usage controls do not replace provider permissions or the reviewer’s decision.

What you leave with: An assisted task with explicit limits.

Availability is confirmed per organization before this operation is enabled.

Continue through supported native and companion access

Native wrappers, companion capture and desktop folder review retain their source behavior and restrictions. A source wrapper is not evidence of store publication or a verified callback destination.

What you leave with: A supported route back to the same account and record.

Availability is confirmed per organization before this operation is enabled.

Find current guides and product explanations

Use searchable Winrove task guides and operation-specific availability. Historical source editions remain in a separate archive; old prices and promises do not become current claims.

What you leave with: A useful explanation connected to the relevant work.

Availability is confirmed per organization before this operation is enabled.

Find help and the applicable notice

Look up task help or prepare an inquiry with the exact reference. Current legal publication and historical originals remain separate; unavailable instruments are never silently replaced.

What you leave with: A clear support route and correctly identified notice.

Availability is confirmed per organization before this operation is enabled.

Reports from verified records

Review outcomes, pricing and source-quality reports with their definitions, reporting period and underlying records. An empty result is not a missing service, and unverified outcomes must not create a win-rate claim.

What you leave with: A source-backed report with its filters, definition and observation time.

Availability is confirmed per organization before this operation is enabled.

Company setup and your first pursuit

Establish the company record, review classifications and past-performance evidence, then set pursuit preferences. This is account and contracting setup; it is separate from employee joining journeys.

What you leave with: A company setup record and a next step into the pursuit workspace.

Availability is confirmed per organization before this operation is enabled.

Capture context beside the source

Review a companion capture, its source location and the destination workspace before saving it. Browser capture, native shells and source-record ownership remain distinct. An installed companion is not proof of an authorized connection.

What you leave with: A reviewed source capture with destination, attribution and permissions.

Availability is confirmed per organization before this operation is enabled.