How to lock a document as read-only to prevent accidental edits inside a card?

Inside Jestor's document tool, you can lock editing on a text linked to a card, making it available for reading only — preventing someone from accidentally typing into a document that shouldn't be changed anymore.

Why do documents linked to a card risk accidental edits?

A document connected to a record, like meeting minutes or a summary of a client conversation, often needs to be frozen once it's finalized. If anyone with access can edit it freely, there's a risk that an accidental change could erase or modify already-recorded information.

How to lock a document in Jestor?

Open the document linked to the card or record.
Use the lock-editing option, available in the document's tools.
With the document locked, anyone with access can read it but can't type or change the content.
If editing is needed again later, simply unlock the document before making the change.

Document state	What you can do
Locked	Read-only, no risk of accidental edits
Unlocked	Normal editing, with every text tool available

Why choose Jestor?

Since each card can have more than one connected document — minutes on top, a summary below, for example — locking each one individually lets you control exactly which content can still be edited and which is already finalized in Jestor.

Frequently Asked Questions

Who can unlock a locked document? Whoever has editing access to that document can unlock it when needed.

Can a locked document still be shared with other people? Yes, you can add people with access even while the document is locked for editing.

Does locking the document prevent viewing the content? No, locking only prevents editing; reading continues to work normally.

Reference video

Get to know Jestor

With Jestor, you can automate workflows, connect departments, and build internal systems your way — all without code and with AI support.

Get to know Jestor at jestor.com and discover how to take your company's management to a new level of efficiency and integration.

How to build an automation roadmap for your company

A good automation roadmap doesn't start by automating everything at once — it starts with a simple starter template, validated with the team, and expands process by process inside a structured BPMS. That's how Jestor recommends starting any implementation. How Do You Build an Automation Roadmap Step

Common mistakes when automating internal processes and how to avoid them

Among the most frequent mistakes automating processes, you'll find automating a poorly mapped process, granting overly broad access to sensitive data, and editing a live workflow without testing it first. Jestor's BPMS, Security, and App Versioning help you avoid exactly these three mistakes. What Are the

How to measure the ROI of a process automation project

Measuring the ROI of process automation requires comparing the tool's cost against the time it saves and the errors it prevents — not just looking at the monthly fee. Jestor's dashboard helps turn this into concrete numbers, comparing before and after automation. How Do You Calculate the

How to identify priority processes to automate first

Priority processes to automate are usually the ones consuming the most team time, generating the most errors, and most affecting the end customer when they go wrong — in that order. Jestor's dashboard and BPMS help you see these three criteria with data, not guesswork. How Do You Prioritize