2026.02.0-pre.01

🚀 Introducing Persistent Personal Views for Editors — Flexibility without breaking workflows

I just adjusted a filter temporarily. Why did the automation stop running?

Who changed this view configuration?

As teams grow and automations become central to operations, shared views become business logic. A small change to filters, grouping, or sorting can silently impact workflows that depend on those views.

To protect teams while preserving flexibility, we’re introducing:

Persistent View Configurations for Editors (Personal Views)

Editors can now fully customise Personal Views, and all their configurations will persist — without affecting shared views used by automations or other users.

🎯 Why This Matters

Shared views often power:

• Automations
• Internal dashboards
• Operational processes
• Team-wide reporting

Even temporary changes in shared views can unintentionally disrupt these workflows.

With this update:

• Shared Views remain stable and protected
• Personal Views provide full customisation freedom
• Automations remain reliable
• Teams can explore data safely

This creates a clear separation:

🔒 Protection Without Limitation

Editors no longer need to compromise between flexibility and safety.

They can:

• Experiment with filters
• Create temporary groupings
• Resize and adjust layout
• Personalize data visibility

All without impacting the rest of the team.