How to Use Attachment Fields Well in a Process

To use attachment fields well, give each document role its own field. One field holding everything makes it impossible to know what a record actually contains.

What one catch-all field costs

The files are there and nobody can tell what they are.

Six documents in one field with no indication of which is which
Automations unable to act on a specific document
OCR unsure which file to read
Required documents not enforceable, since the field is simply non-empty

How to structure them

Decision	Guidance
One field per role	Invoice, contract, proof of delivery
Single or multiple files	Set per field, deliberately
Size limit	Set so uploads fail early rather than silently
Required	Where the process cannot proceed without it
Inline viewing	A PDF block, so nothing is downloaded to review

How to configure it in Jestor

Create one attachment field per document role in Jestor.
Set whether more than one file is allowed, and the size limit.
Add PDF blocks so documents display inside the card rather than downloading.
Enable OCR on the field whose document carries data you would otherwise retype.
Save uploads to a documents table as well, where a document-level view is useful.

Why choose Jestor for document-driven processes?

Jestor can save an uploaded file to both the process table and a documents table, which supports a record-level view and a document-level view of the same file.

Because OCR is configured per field, a record can hold several documents while only the relevant one is read — which keeps page-based usage predictable.

Frequently Asked Questions

Should one field hold every document?

No — one field per document role. See jestor.com.

Can a document display inside the card?

Yes, using a PDF block.

Can a file be saved to two tables?

Yes, to the process table and a documents table.

Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

Get to know Jestor

With Jestor, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by AI. Discover Jestor at jestor.com and see how to take your company's operations to a new level of efficiency and control.

How do you choose an AI tool for professional services operations teams in SMBs?

To choose an AI tool for professional services operations teams in SMBs, look for a platform that combines no-code tables for clients, engagements, and documents with AI features that answer messages, read documents, and summarize data, while keeping professionals in control of advice. In Jestor, these pieces work together,

How do you build a business continuity plan for a services firm?

To build a business continuity plan for a services firm, list critical processes and deadlines, identify risks such as system outages or key person absence, define backup options, assign roles, and test the plan. In Jestor, processes, risks, and actions are connected, so the firm keeps serving clients during disruptions.

What is the best way to run IT security awareness training for staff in a services firm?

A practical way to run IT security awareness training for staff in a services firm is to define short training modules, assign them to all staff, track completion, run simulated phishing tests, and schedule refreshers. In Jestor, staff, modules, and results are connected, so security habits become part of the

How do you route website lead forms to the right team in a services firm?

To route website lead forms to the right team in a services firm, ask for the service and company size in the form, route leads automatically to the right team, set response time targets, record follow-ups, and track conversion by source. In Jestor, forms, leads, and teams are connected,