Skip to main content

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​

ConceptWhat it means
TenantYour company's own space in Cogneris. Users, forms, workflows, templates, documents and settings belong to one tenant and are never visible to another.
RegionWhere 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.
MemberA person of your company with an account in your tenant. Members are invited by an administrator — see Team.
ProfileWhat a member is allowed to see and do, such as administrator or technical team. See Profiles.

Collecting documents​

ConceptWhat it means
FormWhat your customer fills in, designed by your company in the Portal: questions, and the documents to send. See Prepare a form.
Document requestOne 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 linkThe 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.
RequesterThe person outside your company who received the access link and sends the documents.

Processing a case​

ConceptWhat it means
ProcessOne case: everything a requester sent through one access link, filed together in the Document Center with its own folder.
DocumentOne file of a process, with its versions, the data extracted from it and its history.
WorkflowThe steps a process goes through, designed by your company as a graph and published as numbered versions. See Workflow.
PhaseOne 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.
RunOne pass of a process through a workflow. The Runs page lists them.
ReviewA person approving or rejecting each document when a workflow stops for it. Documents wait in a review queue. See Review a document.
Correction roundWhen 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​

ConceptWhat it means
Extraction templateIn 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.
ConfidenceHow 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 templateIn 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​

ConceptWhat it means
EnvelopeOne or more documents sent for signature, with the people who must sign them. See Send an envelope.
SignerA 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​

ConceptWhat it means
API keyThe secret your systems use to call the Cogneris API. Shown once when created; keep it out of code and tickets.
WebhookA 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.
ConnectionIn 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.
MCPA standard way for AI assistants to use Cogneris on your behalf, with tokens your administrator creates. See MCP.