Evidence types
Probo supports two evidence types:| Type | Description |
|---|---|
FILE | A file uploaded directly to Probo (screenshots, reports, exports, logs) |
LINK | A URL pointing to external evidence (a shared drive document, a SaaS report URL, a GitHub PR) |
Evidence states
Each piece of evidence has a state that reflects its completeness:| State | Meaning |
|---|---|
REQUESTED | Evidence has been requested but not yet provided. The task owner needs to supply this item. |
FULFILLED | Evidence has been provided and is ready for review. |
FULFILLED. Evidence pre-created during framework import (from task definitions) starts in the REQUESTED state until a file or link is submitted.
How evidence maps to compliance
The relationship between evidence and your compliance hierarchy is:Uploading file evidence
Navigate to the measure
Open the measure for which you want to provide evidence. You will see the list of tasks associated with that measure.
Select a task
Choose the task that the evidence fulfills. Each task may have requested evidence items that specify what is needed.
Linking URL evidence
If your evidence lives outside Probo (for example, in Google Drive, Notion, or a third-party SaaS), you can provide a URL instead of uploading a file.URLs are stored as-is. Probo does not follow or archive the linked content. Make sure the URL remains accessible to auditors who need to review it.
AI-generated evidence descriptions
When you upload a file, Probo can automatically generate a human-readable description of the evidence content. This description appears alongside the evidence record and helps auditors quickly understand what the file contains without opening it. Description generation is asynchronous. The evidence record has adescription_status field that tracks the generation:
- Pending — description generation has been queued
- Done — description is available
- Failed — generation was unsuccessful (the evidence is still valid; no description will be shown)
Deleting evidence
You can delete any evidence item. Deleting evidence does not affect the task or measure, but the evidence is permanently removed and cannot be recovered. If the evidence was the only fulfilled item for a task, the task’s evidence status returns to outstanding.Evidence in framework exports
When you export a framework as a ZIP archive, Probo includes allFULFILLED file-type evidence for each measure. Evidence of type LINK is not included in the archive (only files can be packaged). See Compliance frameworks for more details on framework exports.
Can one piece of evidence satisfy multiple tasks?
Can one piece of evidence satisfy multiple tasks?
No. Each evidence item is linked to exactly one task within one measure. If the same file or link is relevant to multiple tasks, upload or link it once per task.
What file types are supported?
What file types are supported?
Probo’s file validator accepts common document and image formats. If your file is rejected, check that it is in a recognized format and does not exceed the maximum file size.
Who can upload evidence?
Who can upload evidence?
Any organization member with the appropriate role can upload evidence. Task assignment controls who is responsible for providing evidence, but does not restrict who can upload.
How does evidence relate to audits?
How does evidence relate to audits?
Audits are linked to framework controls. When an audit is in progress, auditors review the measures under each control and examine the evidence attached to their tasks. All fulfilled evidence is available to auditors as part of the audit review.
Compliance frameworks
Understand the hierarchy that evidence fits into.
Policies and documents
Manage policy documents that act as evidence for controls.
Risk management
Link risks to the measures whose evidence demonstrates treatment.
Trust center
Share your compliance posture with customers.