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
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
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,
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
In Jestor, you can register a specific email address on a table and link an AI agent to automatically reply to messages received at that address, with a tone and style defined by whoever sets it up. Why automate email replies Teams that get a high volume of messages at
In Jestor, as soon as a template finishes installing, a notification (an orange dot) shows up in the inbox letting you know the template was installed; clicking it makes a folder with every app and table it generated available. Why this notification is useful Installing a template can take a
Yes. In Jestor, once you enter builder mode for an app, you can switch between the desktop version and the mobile version, organizing the components independently for each one. Why splitting layout by device matters A layout designed for a large computer screen doesn't always work well on
In Jestor, the WhatsApp panel shows, right outside the card, the exact number of messages exchanged in each conversation and the time spent in each phase, plus a full dashboard with data, charts, and indicators for the operation. Why tracking these numbers matters Without visibility into volume and response time,
When structuring a financial BPO in Jestor, the vendor's name, email, and phone fields are usually marked as required, ensuring no vendor gets registered without the minimum data needed for contact and identification. Why setting required fields from the start matters If the registry allows saving a vendor
In Jestor, creating a single-select field (like status) and turning on log metrics makes the system automatically track how long each card stays stuck in each phase, and how long it takes to move between stages. Why measuring this time matters Without this metric, it's hard to
In Jestor, the checklist field lets you choose from ready-made styles — like green/red, yes/no, happy/sad face — or customize it with your own emojis for each item on the internal approval checklist. Why customizing the checklist's style helps An audit or approval checklist is easier
In Jestor, a date-and-time field makes sense when the deadline needs a specific time of day, like "by 3 PM"; a date-range field works better when the payment can happen anytime within a period, with no set time. Why this choice affects deadline control Using