Jestor brought back the sidebar menu because, despite having prioritized app-based navigation in the past, the team realized that offering both options — top menu and sidebar menu — better serves different ways of using the platform. The context behind the decision The sidebar menu was Jestor's original default.
In Jestor, the B key toggles builder mode on any screen, and the C key opens the quick-creation modal, letting you build a new table, app, Kanban, or form without clicking through several menus. Why use keyboard shortcuts day to day Anyone who edits processes often loses time navigating
In Jestor, the single sidebar menu shows one column of navigation, while the double menu splits navigation into two columns, giving more room for item names and longer lists. Why there are two menu options Every team navigates differently: some prefer a more compact, minimalist menu, while others deal with
Yes. In Jestor, every form added to the open card can be independently set as view-only or editable, without that setting affecting the other forms on that same record. Why this flexibility is useful In many processes, part of the information has already been validated and shouldn't
In Jestor, the open card lets you add more than one form in different side panels, each customized for a specific purpose within the same record. Why split information across several panels Putting all of a process's information into one long form makes the card confusing and hard
Yes. For Jestor's fleet management template to work fully with Omie, a low-code integration needs to be set up, done by request via email to Jestor's team. Why this extra step exists The connection between Jestor and Omie for automatic accounts-payable generation depends on
Yes. Although Jestor's fleet management template was originally designed for the towing vertical, it works for any type of fleet, since the layout and indicator placement can be freely changed after installation. Why the base works for other industries The template's structure — vehicles, maintenance, and fuel-
In Jestor's fleet management template, every expense logged for maintenance or fuel automatically generates a matching accounts-payable entry in Omie, without needing to log the amount twice. Why this automation prevents rework Without this integration, the team would log fleet expenses in a spreadsheet or tracking system,
In Jestor's task management template, the dashboard shows a dedicated chart displaying the count of tasks at each priority level — critical, high, medium, and low — separately and visually. Why viewing priority separately helps Without this split, the team would need to open every task to understand what'
Yes. Jestor's task management template is available in the template store both in the standard version and a dark mode version, both working exactly the same way. Why offer both versions Teams have different interface preferences, and some users spend hours a day looking at the task Kanban.
In Jestor, each contact in the sales template has its own chat, where the team logs internal conversations about that specific customer, separate from the contact's data and the external communication channel. Why separate internal chat from contact data Internal discussions about a deal — like "this customer
In Jestor's sales template, if the team tries to move a sale to the next phase without any product added as a line item, the system blocks the action and shows the error "sale with empty sale items." Why this validation exists A sale with no