> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to Use Attachment Fields Well in a Process
- URL: https://blog.jestor.com/use-attachment-fields-well/
- Published: 2026-09-17T22:37:48.000Z
- Updated: 2026-09-17T22:37:48.000Z
- Author: Bruno Bannach

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

1. Create one attachment field per document role in **Jestor**.
2. Set whether more than one file is allowed, and the size limit.
3. Add PDF blocks so documents display inside the card rather than downloading.
4. Enable OCR on the field whose document carries data you would otherwise retype.
5. 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](https://jestor.com/?ref=blog.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](https://jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.