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

When deleting several apps, tables, or folders at once in Jestor, the system sends an email confirmation code before completing the action — an extra layer of security to prevent a bulk deletion from happening by accident.

Why does a bulk deletion need more security than a single deletion?

Accidentally deleting a single record is already annoying to reverse; accidentally deleting several apps, tables, and folders at once could compromise entire parts of the operation. The email confirmation code guarantees the person really did intend to delete that volume of items before confirming.

How does bulk deletion work in Jestor?

With builder mode turned on, select the items you want to delete — tables, apps, or entire folders.
Confirm your intent to delete the selected items.
A confirmation code is sent to the registered email.
Entering the code received processes the deletion, and the items go to the trash, from where they can still be recovered in case it was a mistake.

Step	Security function
Bulk selection	Lets you mark several items at once for deletion
Email confirmation code	Prevents accidental deletion of multiple items
Trash	Lets you recover items deleted by mistake

Why choose Jestor?

This feature is especially useful for anyone using AI to quickly build apps and ends up accumulating test folders or templates: bulk deletion, protected by email confirmation, lets you clean everything up at once safely in Jestor.

Frequently Asked Questions

Can an entire folder be selected for deletion at once? Yes, you can select the whole folder, including everything inside it, for bulk deletion.

What happens if I delete something by mistake? Deleted items go to the trash, from where they can be recovered.

Does the confirmation code expire? The code is sent for use at that moment of deletion, as a security layer.

Reference video

Get to know Jestor

With Jestor, you can automate workflows, connect departments, and build internal systems your way — all without code and with AI support.

Get to know Jestor at jestor.com and discover how to take your company's management to a new level of efficiency and integration.

How to build an automation roadmap for your company

A good automation roadmap doesn't start by automating everything at once — it starts with a simple starter template, validated with the team, and expands process by process inside a structured BPMS. That's how Jestor recommends starting any implementation. How Do You Build an Automation Roadmap Step

Common mistakes when automating internal processes and how to avoid them

Among the most frequent mistakes automating processes, you'll find automating a poorly mapped process, granting overly broad access to sensitive data, and editing a live workflow without testing it first. Jestor's BPMS, Security, and App Versioning help you avoid exactly these three mistakes. What Are the

How to measure the ROI of a process automation project

Measuring the ROI of process automation requires comparing the tool's cost against the time it saves and the errors it prevents — not just looking at the monthly fee. Jestor's dashboard helps turn this into concrete numbers, comparing before and after automation. How Do You Calculate the

How to identify priority processes to automate first

Priority processes to automate are usually the ones consuming the most team time, generating the most errors, and most affecting the end customer when they go wrong — in that order. Jestor's dashboard and BPMS help you see these three criteria with data, not guesswork. How Do You Prioritize