File your AI evidence where the rest of your compliance record lives
VeriProof files the evidence reports you approve in your ComplyAssistant account, under the document types your team already uses.
- Used by
- Compliance and audit
- What's shared
- VeriProof to ComplyAssistant. Only delivery confirmations come back.
- Set up by
- A VeriProof administrator, once VeriProof’s team approves your ComplyAssistant account
Where each report lands
| VeriProof report | ComplyAssistant document type | Automatic timing |
|---|---|---|
| AI governance summary | AI Governance Assurance | Weekly |
| Application and model inventory | Operational Evidence | Monthly |
| Exceptions and remediation | Issue Documentation | Monthly |
| Runtime safeguards and human review | Session Evidence Pack | Weekly |
| Agentic Trust Controls, HIPAA, NIST AI RMF, ISO/IEC 42001, EU AI Act, and SOC 2 summaries | Framework Compliance Report | When a new saved assessment completes its required reviews |
Document type names have to match exactly. If one is missing, add it under Account Settings → Dynamic Fields → Document Types in ComplyAssistant. A report with no matching type stays preview-only.
Approve the first report, then turn on automatic sending
Every report starts in manual mode. You open it, check the exact PDF and where it's going, and send it. Once ComplyAssistant confirms it arrived, you can turn on automatic sending for that report and set of applications.
If you change what a report includes, VeriProof asks for a new reviewed send before automatic delivery resumes.
What leaves VeriProof
Reports are PDFs. They can include application, model, and rule names, the display names of people involved, and approved public links, so check those before you send. Email addresses, raw content, private review rationale, and free-text notes are left out, and prompts and model responses stay in VeriProof.
VeriProof only adds reports to ComplyAssistant. It doesn't read your documents or assessments. The access token is stored encrypted. Disconnecting stops delivery and deletes the token from VeriProof. You can also revoke it in ComplyAssistant.
Connect ComplyAssistant
An administrator who manages integrations connects the account. Administrators and compliance officers with evidence export permission manage the reports.
Ask us to approve your account
VeriProof's team adds your ComplyAssistant web address to the approved list for your organization.
Copy an access token
In ComplyAssistant, open your account settings from your name in the header. The Access Token is near the bottom. Use the account that will receive the reports.
Connect in VeriProof
In Settings → ComplyAssistant, enter your ComplyAssistant web address and the token. Saving sends nothing yet.
Choose applications and send the first report
Pick the applications reports cover, preview a report, and send it.
Permissions VeriProof requests
| Permission | Access | Purpose |
|---|---|---|
| Account access token | Write | Upload the reports you approve into the receiving account |
Often used with
Put your AI evidence in the same place as the rest
We'll set up your ComplyAssistant connection with you, starting from the reports your auditors ask for.