Why is an email confirmation code required before a bulk deletion?

In Jestor, deleting several apps, tables, or an entire folder at once requires a confirmation code sent by email before the deletion is finalized, as an extra layer of security against accidental mass deletions.

How this security layer works

After selecting the items to be bulk deleted, Jestor lists everything about to be removed and, to confirm, sends a code to the registered email. Only after entering that code is the deletion actually carried out. Even so, deleted items go to a trash bin, from which they can be recovered if the deletion was done by mistake.

Security layer	Function
Email code	Confirms it was really the user who requested the deletion
Trash bin	Lets you recover items deleted by mistake

How to safely do a bulk deletion

Turn on builder mode.
Select the apps, tables, or folder you want to delete.
Review the list of items that will be deleted.
Enter the confirmation code sent by email to finalize the deletion.

Why choose Jestor

Protection against mistakes: the email code prevents accidental bulk deletions.
Recovery trash bin: even after confirmation, the deletion can be reversed from the trash bin.
Faster cleanup: accounts with lots of tests or AI-generated folders can be cleaned up in just a few clicks.

Is the confirmation code sent for every deletion, even of a single item?

The confirmation code was introduced specifically for bulk deletions involving multiple apps, tables, or entire folders.

Can you recover an item after the deletion has already been confirmed with the code?

Yes, deleted items go to the trash bin, from which they can be recovered afterward.

Is this feature useful for people using AI to build apps?

Yes, it's especially useful for anyone using AI to create apps, since that process can generate several folders and templates that later need to be cleaned up quickly.

Reference video

Check out more hands-on tutorials on the Jestor YouTube channel.

Get to know Jestor

With Jestor, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by AI.

Discover Jestor at jestor.com and see how to take your company's operations to a new level of efficiency and control.

Why does a removed user show as inactive instead of being deleted, and what does that preserve in the history?

In Jestor, removing a user doesn't delete them from the system: their status changes to inactive, specifically to preserve the history of everything that person changed on records in the past. Why this logic exists If a user were completely deleted, the entire history of actions they performed

Can a text inside a card be shared with only the selected people?

Yes. In Jestor, each document connected to a card can be shared with only the specific people added to it, giving individual access instead of automatically opening it up to the whole team. How selective sharing works When creating a document inside a record, you need to manually add the

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

In Jestor, any document connected to a card can be locked for editing, making it read-only, which prevents someone from accidentally changing the content when reading that text. How locking a document works Inside the documents tool (Docs) connected to records and cards, you can lock a specific text

Where can you activate the builder directly from the Home to quickly access editing mode?

In Jestor, you can add the builder block directly to the home page, letting you access construction mode quickly with no need to first navigate to another app. How to add the builder to the Home When personalizing the Home, one of the available blocks is the builder option, which