Vision administration overview
This chapter was written from the product's source code and has not yet been checked by a person on a running Cogneris. If what you see on screen differs, the screen is right — please tell your Cogneris contact so the chapter can be corrected.
Vision is the document-AI product of Cogneris. In Vision you define templates — the document types your company receives and the fields to read from each — try them on real documents, tune the AI agent that extracts them, and manage the keys and webhooks that let your own systems call the Cogneris API. Workflow phases such as Classification, Extraction and Cross-check use what you configure here.
| How to get here | Open the Vision product from the Cogneris platform. Embedded in the platform, Vision's menu appears in the platform's left column and the platform shows one breadcrumb bar; opened on its own, Vision shows its own menu (branded Cogneris Vision), its own breadcrumb starting at Vision, and a Log out button. |
| Who can use it | Any signed-in member of your company can open Vision. Templates additionally require Vision access on your membership (see Who can use what). |
| Content status | From source; not observed (vision-fe 0b724a0, vision-be fce7fcc, 2026-10-22) |
What you manage in Vision
| You want to | Menu | Chapter |
|---|---|---|
| See how many documents and pages Vision processed in the last 30 days | Dashboard | Dashboard |
| Create a template from sample documents, follow its provisioning, rename or delete it | Templates | Templates — list and create |
| Define the fields a template extracts, test a field's prompt and publish the template | Templates › a template › Schema | Template schema |
| Decide what is masked in a template's documents | Templates › a template › Redaction | Template redaction |
| Choose how the AI agent extracts a template: mode, models, retries, domain agents, budget, run history | Templates › a template › Agent | Template agent |
| Try classification, extraction, split, crop and redaction on a document | Playground | Playground |
| Connect an editor (VS Code, Cursor, Claude Code) to the Cogneris MCP server | MCP | MCP |
| Set company-wide guardrails for the AI agent, read its analytics, review fraud alerts | Tenant agent settings (Guards, Analytics, Review) | Tenant agent settings |
| Create API keys, register webhook endpoints, read API and webhook logs | Developers › API Keys, Webhook Endpoints, API Request Logs, Webhook Request Logs | Developers |
Menu and navigation
The menu has six entries, in this order:
| Menu entry | Opens | Notes |
|---|---|---|
| Dashboard | The Vision home | Also where Vision opens when no page is named. |
| Templates | The template list | A template opens in the template editor, on its Schema tab. The editor's other tabs are Redaction and Agent; Agent has the sub-tabs Mode, Router, Retry, Domain agents, Budget and History. |
| Playground | The test bench for one document | — |
| MCP | Editor connection instructions | The former in-app Chat was replaced by this page; an old Chat link opens MCP. |
| Tenant agent settings | Company-wide agent settings | Opens on the Guards tab; the other tabs are Analytics and Review. |
| Developers | A group of four pages | API Keys (also what opens for the group itself), Webhook Endpoints, API Request Logs, Webhook Request Logs. |
Every page has an address of its own, so a link to a page (for example a template's Agent › Budget tab) opens that page directly. Addresses of pages that used to live in the platform keep working.
Sign-in. Vision has no sign-in page of its own. Opening any Vision page without a session sends you to the Cogneris sign-in and brings you back to the page you asked for.
A page that does not exist shows 404 and Page not found, with a Go home button that opens the Dashboard.
Who can use what
Vision itself does not hide menu entries by profile: every signed-in member sees the whole menu. What you may do is checked by the Vision service on each request.
| Area | Checked by the service |
|---|---|
| Templates (create, list, open, save, rename, delete, add or remove sample documents) | Your company membership must be active and must include access to Vision. The check is made live on each request, so a revoked access takes effect at once; if the check cannot be made (for example the billing service is unavailable), the request is refused. |
| Templates › Redaction (changing a redaction policy) | A company administrator. See Template redaction. |
| Dashboard usage figures | A signed-in member of the company. The Active Templates tile reads the template list, so it is subject to the Templates check above. |
| Other areas | Each chapter states its own checks in its Who can use it row. |
Everything you see in Vision belongs to your company only: templates, usage, keys and logs are always scoped to your company.
How Vision relates to Workflow
Workflow runs your processes; Vision does the document work for some of its phases. What you configure in Vision changes what those phases do:
| Workflow phase | What it takes from Vision |
|---|---|
| Classification | The document type, and the template of your company that covers that type. Only templates that were saved and provisioned take part in classification; see Statuses in Templates — list and create. When your company has no provisioned template at all, classification falls back to zero-shot classification. |
| Extraction | The fields declared in the template that classification found (see Template schema). |
| Split and Crops | The Vision service finds the segments of a file and the regions to cut. You can try split and crop on a document in the Playground. |
| Cross-check | The template list, to choose a document role and to suggest the template's field names. The list includes templates in every status, including Draft; see What a Draft means elsewhere in Templates — list and create. |
Classification resolves the template by its name: the document type returned by the classifier is matched to a template whose title equals it (ignoring case, and treating spaces, hyphens and underscores alike). Keep template titles stable once Workflow processes depend on them.
How Vision relates to the Cogneris API
Your own systems reach the same document work through the Cogneris API, authenticated with the API keys created in Developers › API Keys, and they are told about results through the endpoints registered in Developers › Webhook Endpoints. The API only accepts templates that are published (status Finished). See Developers.
Where to start
- Look at the Dashboard to see whether Vision is already processing documents for your company.
- Create a template for each document type you receive — Templates — list and create — then define its fields and save it in Template schema. Saving provisions the template; until then it is a Draft and takes no part in classification.
- Try it on a real document in the Playground.
- Optionally, tune extraction per template in Template agent and mask sensitive data in Template redaction; set company-wide limits in Tenant agent settings.
- Use it: in a Workflow, add Classification and Extraction phases; from your own systems, create an API key and a webhook endpoint in Developers. To build against the API from an editor, see MCP.
Related
- Dashboard
- Templates — list and create
- Developers
- Workflow phases: Classification, Extraction, Cross-check
Last reviewed 2026-10-22 · Version 1.0.0 · Owner: product-documentation