Core concepts
These are the words the rest of the documentation uses. Each one links to where it is explained in full.
Your company in Cogneris
| Concept | What it means |
|---|---|
| Tenant | Your company's own space in Cogneris. Users, forms, workflows, templates, documents and settings belong to one tenant and are never visible to another. |
| Region | Where your tenant lives: Europe (where new tenants are created) or the United States. The region decides which addresses you use, for example api-eu.cogneris.ai or api-us.cogneris.ai for the API. |
| Member | A person of your company with an account in your tenant. Members are invited by an administrator — see Team. |
| Profile | What a member is allowed to see and do, such as administrator or technical team. See Profiles. |
Collecting documents
| Concept | What it means |
|---|---|
| Form | What your customer fills in, designed by your company in the Portal: questions, and the documents to send. See Prepare a form. |
| Document request | One document a form asks for — an identity card, a proof of address, a selfie. A request can repeat once per value of a form field, for example once per person listed. |
| Access link | The personal, secure link a customer receives to open a form. It has a deadline, can be limited in the number of accesses, and can be revoked. The screens also call it a magic link. See Send an access link. |
| Requester | The person outside your company who received the access link and sends the documents. |
Processing a case
| Concept | What it means |
|---|---|
| Process | One case: everything a requester sent through one access link, filed together in the Document Center with its own folder. |
| Document | One file of a process, with its versions, the data extracted from it and its history. |
| Workflow | The steps a process goes through, designed by your company as a graph and published as numbered versions. See Workflow. |
| Phase | One step of a workflow: classify, extract, cross-check, face match, call your system, decide, review, generate a document, sign, deliver. Each phase is described in Workflow phases. |
| Run | One pass of a process through a workflow. The Runs page lists them. |
| Review | A person approving or rejecting each document when a workflow stops for it. Documents wait in a review queue. See Review a document. |
| Correction round | When a reviewer rejects a document of a process that came through the Portal, the requester gets a new link and resends only what was rejected. See Return a document for correction. |
Document AI and generated documents
| Concept | What it means |
|---|---|
| Extraction template | In Vision, the definition of a document type and the fields to read from it — names, dates, amounts, tables. Also used to recognise the type of a document. See Vision. |
| Confidence | How sure the AI is of a value it read, from 0 to 100 %. Low confidence is one of the reasons a document goes to review. |
| Document template | In Template, a Word file with placeholders that becomes a finished document — a declaration, a contract — filled with the data of a case. Not the same as an extraction template. See Template. |
Signing
| Concept | What it means |
|---|---|
| Envelope | One or more documents sent for signature, with the people who must sign them. See Send an envelope. |
| Signer | A person who signs an envelope. They confirm who they are with a code sent by e-mail before they can see and sign the documents. |
Connecting your systems
| Concept | What it means |
|---|---|
| API key | The secret your systems use to call the Cogneris API. Shown once when created; keep it out of code and tickets. |
| Webhook | A call Cogneris makes to your system when something happens — a document was processed, a workflow finished — so you do not have to ask. Each call is signed so your system can check it came from Cogneris. |
| Connection | In Workflow, the address and credentials of one of your systems, used by the REST integration phase. Credentials live in the connection, never in the workflow. |
| MCP | A standard way for AI assistants to use Cogneris on your behalf, with tokens your administrator creates. See MCP. |