SEARCH
Search the request catalogue to find the document types your organisation already asks for, so a checklist drafted in chat maps to real request items.
AI Assistant Connector
The CVOR connector lets an approved AI assistant search your request types, preview a batch of document requests and create the batch that was previewed. The assistant never sees a document or an upload link.
The CVOR connector is a separate, optional service that lets an approved AI assistant prepare and create document requests inside CVOR. It works on Document Requests: asking a named person for specific documents and receiving them encrypted in the browser.
The assistant handles the asking. CVOR handles everything that happens to the documents afterwards, from the invitation link to access, retention and deletion.
SEARCH
Search the request catalogue to find the document types your organisation already asks for, so a checklist drafted in chat maps to real request items.
LIST PROGRAMMES
List the programmes a request can belong to, such as an onboarding cohort or a client intake, each with its own retention period.
PREVIEW
Preview a batch of document requests before anything is created. Nothing is sent while the batch is only a preview.
CREATE
Create only the batch that was previewed. Creation is all-or-nothing, so a batch is created whole or not at all.
The connector exposes no documents and no upload links. An assistant cannot read what a person submitted, open a file or hand a link to anyone.
It cannot create a request that was not previewed, and it covers Document Requests only, so Data Room rooms and their participants are outside its reach. Documents stay encrypted in the submitter's browser to the organisation's key, and reviewers open them inside CVOR with the organisation vault.
Only an organisation owner or administrator can approve the connection. After that, every call rechecks three things: the connection itself, the membership behind it and the organisation's access to the product.
A withdrawn approval or a removed member therefore takes effect on the next call, with no separate clean-up step.
01
An HR manager asks the assistant for a new-starter document checklist. The assistant searches the request catalogue and matches each item to a document type CVOR already asks for.
02
The assistant prepares a batch for the people and programme named and shows a preview. No request exists yet, so nothing has reached a recipient.
03
Each recipient gets their own request package, listing up to 50 items, with a single-use link that expires after 7 days. One send reaches up to five recipients.
04
Each upload is encrypted in the recipient's browser. Request status moves from pending to partially fulfilled to fulfilled, and every view and download by your team is recorded.
Organisations are onboarded by CVOR, and MCP and API automation is an add-on that a plan either includes or leaves out. Owners and administrators can see their plan and usage.
No. The connector exposes no documents and no upload links. Documents are encrypted in the submitter's browser, and the assistant only works with the request catalogue, programmes and request batches.
No. The connector is preview-first and creates only the batch that was previewed. Batch creation is all-or-nothing, so a batch is created whole or not at all.
The connector does not read documents. CVOR Assist, the in-product command panel, is rule-based and does not use a language model. Separately, organisations can enable optional AI review, which receives pseudonymised extracted text for an advisory review that only the reviewer sees. Pseudonymisation is best effort, so redaction can miss personal information.
No. The connector covers Document Requests only: asking a named person for specific documents and receiving them encrypted.
Approved AI agents that connect through the CVOR customer MCP connector. An organisation owner or administrator approves each connection.
We review the documents you request, who approves them and which assistants your team uses before onboarding.