General settings

Settings → General is the home for project-wide controls — auto-scan threshold, classifier behavior, duplicate detection, document lock, project name and mailbox. Most setup decisions happen here on day one.

This page walks through each control, what it does, and when to change it.

Project name

Free text. Renameable anytime. The new name shows everywhere the old one did — Dashboard, sidebar, breadcrumbs, search.

Renaming doesn't change the project's email mailbox or affect any integrations.

Project mailbox

Read-only. Shown so you can copy it for supplier instructions, mail forwarding rules, etc. The format is {project-type}-{random}@mail.recognito.io.

The random suffix stays stable across renames. Once you point suppliers at this address, you can keep using it indefinitely.

For the full email-path behavior, see Email inbox.

Auto-scan page threshold

The page count above which Recognito holds off on extraction until the user picks pages.

Documents below the threshold flow straight through Processing → Done. Documents above the threshold land in Needs action first — the user opens the document, clicks Process, and picks which pages to actually scan.

Defaults:

• 5 pages is the typical default.
• Unlimited turns the threshold off — every document goes straight to processing regardless of size.

How you might set it, depending on your documents:

Setting	When it fits
5 pages	The default. Catches accidentally-large uploads.
Higher (10–20)	Suppliers who routinely send longer invoices, so reviewers aren't sent to Needs action on every document.
Unlimited	You trust uploaders not to send 200-page PDFs by mistake.

Raise the threshold for known-long document streams

If your suppliers routinely send 10-page invoices, leaving the threshold at 5 means every document hits Needs action — annoying for reviewers. Raising it to 15 saves the clicks without losing the safety rail.

Classify uploaded files

Toggle that controls whether the classifier runs on multi-file email uploads.

When on: a multi-file email gets its attachments classified by document type. Files matching one of the project's Accepted document types become standalone documents; others become attachments.

When off: every attachment in a multi-file email becomes its own document. No grouping.

The classifier only runs on email uploads — manual uploads and API uploads bypass it.

See Email inbox for the full classifier behavior.

Accepted document types

The list of document types the classifier recognizes. By default, this is just the project's primary type (e.g., Invoice). You can add more if your project handles multiple types — invoices and purchase orders, say.

A project's Accepted document types affect both the classifier and any per-type extraction logic. If you change this list, test on representative emails before pointing real volume at the project.

Reject duplicate files

File-hash duplicate detection. When on, Recognito computes a hash of every incoming file and rejects uploads whose hash matches an existing document.

• The file is not saved.
• No Duplicate Approval Status is set (because no document gets created).
• No charge to the page quota.

This is one of two duplicate-detection layers — the file-hash check. The other layer, Duplicate Checker fields (configured in Settings → Field Usage), checks for duplicates based on extracted field values rather than file bytes.

Layer	Trigger	Document saved?	Page quota?
File hash (this setting)	Upload	No	No
Field-value (Field Usage)	After extraction	Yes, with Duplicate Approval Status	Yes

Most projects benefit from turning file-hash rejection on — it's cheap and definitive. Field-value duplicate detection is the more nuanced layer, useful for catching the same logical document re-sent with different file bytes.

File-hash duplicates disappear silently

When a file gets rejected by the hash check, no document is created — there's no entry in the Documents view, no audit trail. If a supplier reports "I sent you the invoice," check both your project's documents and whether duplicate rejection might have eaten it.

Document lock settings

Per-category controls for read-only behavior at specific statuses.

For each of the five field categories (Main, Table, Payment, Tax, Metadata), you can configure:

• Lock when Approved — fields become read-only once the document reaches Approved Approval Status.
• Lock when Validated — fields become read-only at Validated.
• Lock when Rejected — fields become read-only at Rejected.
• Lock when Exported — fields become read-only at Exported Document Status.

The four toggles are multi-select — you can lock a category at multiple statuses if the document might pass through them.

Override-permission users bypass locks. Default users see them as a hard stop.

What lives elsewhere (not in General)

A few things admins look for in General that actually live in other sub-sections:

• Field schema — Settings → Document fields.
• Field appearance in columns / filters / clipboard — Settings → Field Usage.
• Mapping rules — Settings → Mapping.
• Users and permissions — Settings → Users.
• Webhooks and integrations — Settings → Integrations.
• Custom Response Schema — Settings → Developers.
• Notifications — Settings → Notifications.

If you can't find a setting in General, it's almost certainly in one of the others above.

What's next

• Projects & organizations — the scoping that frames every General setting.
• Email inbox — the classifier and email path in depth.
• Document types — what each project type provides out of the box.
• Audit & history — how to see who changed what.