Can Form Fields Become Read-Only After a Record Is Approved?

Yes. In Jestor, one of the forms inside an open card can be configured to become read-only, following the process's conditional rules — for example, locking editing as soon as a record is approved.

How does this edit lock work?

The specific form is marked as read-only, and that condition can be linked to the record's stage or status, so editing only gets blocked from the moment approval happens.

What changes on the form before and after approval?

Form state	Before approval	After approval
Editing	Fields editable normally	Form locked as read-only
History	Still being built	Preserves exactly what was approved
Other forms on the card	Can remain editable, if configured that way	Follow their own rule, independent of this one

Why choose Jestor for approval processes?

Jestor lets a card have several independent forms, each with its own editing rules, giving precise control over what can or can't be changed at each step of the process.

Does the read-only lock apply to the whole card or just one form?

It can be applied to a specific form within the card, without affecting the others.

Can this setting depend on the process stage?

Yes, the form can automatically become read-only from a specific stage or status onward, such as approved.

Can this be combined with other conditionals on the same card?

Yes, each form on the open card can have its own conditional rules, including editing and visibility.

Video Tutorial: Step by Step

Check out more practical tutorials on Jestor's YouTube channel.

Get to know Jestor

With Jestor, already-approved information can be protected from editing, keeping the process history reliable.

Get to know Jestor at jestor.com and see how to take your operation's efficiency to a new level.

How Do You Set a Different Homepage for Each Role as Soon as the User Logs In?

In Jestor, when editing a role, you can paste the link to a specific page (like a dashboard) into the homepage field, so that every user with that role lands directly there as soon as they log in. Why this improves the user experience Without this setting, everyone would land

What's the Access Difference Between a Member-Type User and a Builder-Type User?

In Jestor, a member-type user is meant for anyone who just uses already-configured processes, while a builder has access to create and edit tables, apps, automations, and the account's structure. Why separate these two access levels Not everyone on the team should be able to change

Why Does Grouping Tables and Apps for the Same Process Into the Same Folder Make Maintenance Easier?

In Jestor, grouping tables and applications for the same process into a single folder makes it quick to find everything related to a specific Kanban or flow, saving you from wasting time hunting for scattered pieces across the platform. Why folder organization avoids clutter Just like an unorganized computer desktop,

Can You Duplicate an Entire Application, With All Its Elements, Right From the Action Bar?

Yes. In Jestor, the action bar (opened with Ctrl+K or Cmd+K) lets you clone an entire application, with every element it contains, just by choosing the source app and giving the copy a new name. Why cloning from the action bar is faster Manually rebuilding an app from