Why Viewing the Change History Can Be Restricted to Only the System's Builder Users

In Jestor, the updates tab that shows a record's change history can be configured to appear only for builder-type users, keeping that level of detail out of view for people who just use the process day to day.

Why does restricting this history make sense?

Not every piece of change information needs to be visible to people who just fill out forms and follow the process. Limiting this view to builders prevents technical or sensitive details from showing up for the whole team.

Who sees what in the updates tab?

Setting	Who sees the update history
Off (default)	No one sees the updates tab
On for everyone	Anyone with access to the record
On for builders only	Only builder-type users

Why choose Jestor to control who sees what?

Jestor separates the updates tab from regular chat, giving control over who follows the technical change history without mixing it into everyday conversation about the record.

Is the updates tab enabled by default?

No, it comes disabled by default and needs to be turned on in the form settings.

Can updates also appear in chat?

Yes, it's possible to configure updates to also be sent to chat, the way it worked before.

Does restricting to builders block everyone else from seeing changes?

Yes, with that option checked, only builder-type users can view the updates tab.

Video Tutorial: Step by Step

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

Get to know Jestor

With Jestor, you decide who follows a record's technical history and who only sees the essentials.

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