We've just rolled out Smart Confirmation Guardrails to prevent accidental data loss while keeping your workflow smooth and efficient.

What's New?

Destructive actions now show clear consequences before you commit. No more "oops" moments.

In primary environments, high-risk changes affecting 10+ records require explicit confirmation by typing what you're destroying (e.g., "delete author_name field in 2k+ records"), while smaller changes use lighter confirmations to keep your workflow fast. Sandboxes remain unrestricted for rapid iteration.

How Does It Work?

When you attempt a destructive action in your primary environment, the system calculates potential impact.

If 10+ records will be affected, it shows a detailed confirmation dialog with exactly what will be deleted or modified, how many records will be impacted, and a confirmation phrase to type that reinforces the consequences.

If fewer than 10 records will be affected, a simpler dialog will be shown that doesn't require a confirmation phrase.

Why Does It Matter?

Accidentally deleting a model, converting a field type, or removing a locale can cause massive data loss, broken references, and hours of recovery work. These guardrails give you safety without friction — protection appears exactly when and where you need it most.

This is especially valuable for:

• Enterprise teams managing large-scale content operations with thousands of records

• Multi-locale projects where removing a language could affect hundreds of assets and records

• Complex schemas with interconnected models and references

You get enterprise-ready protection with smart defaults: your production environment stays safe, while development environments stay fast.