Evidence: Record provenance, permitted sharing and revocation
Existing records · In development
A shared view does not transfer ownership or expose personal records.
Open in the applicationWINROVE / EVIDENCE
Keep the record behind the decision.
We're expanding Winrove's evidence workflows so the original file, its source and its permitted use stay attached to every decision it supports.
In development Availability claims follow dated product receipts; the companion product build is still in progress.
For every workspace, within permissions
- 01
Source
A record enters with its origin: where it came from and who contributed it.
- 02
Version
Each version keeps who changed it and when; earlier versions are never rewritten.
- 03
Purpose
Sharing names a recipient and a purpose. Access follows the stated purpose.
- 04
Review
Decisions, exceptions and review history stay attached to the record.
- 05
Use
A permitted use is a scoped export. It does not transfer ownership of the record.
A worked example.
- Original
- Site survey · October field visit (unchanged)
- Linked to
- SYN-001 delivery record; compliance review R-11
- Shared with
- Maya · receiving authority review
- Purpose
- October service report review
- Access state
- Active · revocable
Sharing grants access for a named purpose. It does not transfer ownership, and a downloaded copy cannot be recalled.
Source rights
A record keeps the rights of its source. Sharing it into a workspace does not transfer ownership.
Freshness
Records age. Review history shows when a record was last verified, so stale evidence stays visible rather than silent.
Reuse
One original can support a delivery record and a workforce example. Each reuse names its own purpose.
Revocation
Access can be revoked. Revocation ends further access; it cannot recall a copy that was already downloaded.
What an export contains
An original-file package is more than a manifest: the originals, the index, the decisions and the exclusions that shaped it.
Operation availability.
Each advertised operation carries its own state. These are derived from dated product receipts; a page or an endpoint alone does not make an operation live.
Original records
In developmentOriginal files stay unchanged with their source context.
Version history
In developmentEach version keeps who changed it and when.
Purpose-bound sharing
In developmentAccess follows the stated purpose and can be revoked.
Review history
In developmentDecisions and exceptions remain attached to the record.
Scoped exports
In developmentAn export packages originals, index and decisions; it cannot recall a copy already downloaded.
Questions that come up.
Does sharing transfer ownership?
No. Sharing grants access to a named recipient for a stated purpose. The record keeps the rights of its source.
Can revoked access recall a download?
No. Revocation ends further access. A copy already downloaded cannot be recalled; that limit is part of the sharing decision.
What is in an original-file package?
The originals, an index, the decisions recorded against them and the exclusions. A manifest alone is not the package.
How does evidence connect to delivery?
A delivery decision links to the record behind it: the file, its version and the review it was part of.
Does evidence expire?
Records carry freshness: review history shows when they were last verified, so stale supporting material stays visible.
Operation availability
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.