Every User Gets a Personalized Workspace

A saved view captures everything about how you interact with a collection's data:

View: "Q2 Pipeline Review" Collection: deals View Type: kanban Sort: -value DESC, -createdAt DESC Columns: [name, company, stage, value, closeDate, owner] Filter: { stage: { notIn: ["Closed Won", "Closed Lost"] }, closeDate: { gte: "2026-04-01", lte: "2026-06-30" }, owner: { equals: "$currentUser" } } Grouping: { by: "stage", aggregate: "sum:value" } Conditional Formatting: [ { field: "value", op: "gte", value: 50000, style: { badge: "green" } }, { field: "closeDate", op: "lt", value: "$today", style: { highlight: "red" } } ]

Switch to this view and the collection immediately shows:

• Kanban board grouped by deal stage
• Only deals closing Q2, owned by you, excluding closed deals
• Columns showing name, company, stage, value, close date, owner
• Deals over $50K get green badges
• Overdue deals get red highlights
• Board sorted by value descending within each stage

One click. Every preference applied at once.

The Saved Views Menu

Every collection toolbar in the Aeion admin has a Saved Views button (bookmark icon). Click it to:

1. View the list — All your saved views for this collection, plus any shared views from teammates
2. Apply a view — Click any view to instantly apply its filter, sort, columns, grouping, and view type
3. Save current state — Hit "Save Current View" to capture your current configuration under a name
4. Rename / Delete / Set Default — Hover actions on each saved view
5. Share with team — Toggle "Shared" on any view to make it visible to other tenant users

Views Live in Your Database

Views are stored server-side, scoped to your tenant — not in browser localStorage or URL parameters. A saved view captures its name, which collection it applies to, its view type (list, kanban, calendar, gallery, or gantt), filter, sort, visible columns, grouping and aggregation rules, conditional formatting rules, default status, and sharing status.

Access control: Users can only see and edit their own views, plus any shared views. Admins can delete any view. Setting a new default automatically and atomically unsets the previous one — there's never ambiguity about which view loads.

Dashboards are the second piece of the Views module — visual workspaces assembled from widgets across all modules.

Dashboard: "Operations Command Center" Widgets: - CRM pipeline revenue by stage (from CRM module) - Commerce today's orders + revenue (from Commerce module) - Helpdesk open tickets by priority (from Helpdesk module) - Fulfillment shipments in transit (from Fulfillment module) - Finance AP aging buckets (from Finance module) Layout: 2-column grid, widgets sized and positioned Shared: true (entire ops team sees it) Default: true (loads as home dashboard for ops users)

Each dashboard stores a name, an optional description, its grid layout with widget placement and sizing, default status, sharing status, and who created it.

Widget catalog: Every module contributes its own widgets to a shared catalog. When you add a widget to your dashboard, Aeion places it at the grid position you choose — no manual wiring between modules required.

Saved views and dashboards use the same straightforward sharing model:

read: your own views, plus anything a teammate has shared create: any authenticated user update: the owner, or a tenant admin delete: the owner, or a tenant admin

Auto-unsetting defaults: Only one view per collection can be your default at a time. When you mark a new view as your default, Aeion automatically clears the flag on your previous default in the same operation — there's never a moment where two views both claim to be "the" default, and no manual cleanup required.

Scenario: You have "My Default Pipeline" set as your default. You create "Q3 Focus View" and check "Set as default." Aeion automatically un-defaults "My Default Pipeline" for you — only one default per collection per user, always.

Saved views use Aeion's standard filter syntax, so anything you can build in the collection filter bar can also be saved, shared, and reapplied:

```typescript // Filter examples

{ status: { equals: "active" } } // Simple equality

{ createdAt: { gte: "2026-01-01", lt: "2026-07-01" } } // Date range (relative dates supported: "$today", "$now", "$week", etc.)

{ stage: { in: ["Negotiation", "Proposal"] } } // IN clause

{ assignedTo: { equals: "$currentUser" } } // Current user substitution — view always shows user's own records

{ or: [ { value: { gte: 50000 } }, { priority: { equals: "high" } } ] } // OR group with AND inside

{ name: { contains: "acme" }, status: { equals: "active" } } // AND implicit between top-level keys

{ tags: { arrayContains: "enterprise" } } // Array contains ```

Sort format: "fieldName" or "-fieldName" (descending). Example: "-value,createdAt" = sort by value descending, then by createdAt ascending within ties.

Column format: Array of field names in display order: ["name", "company", "value", "stage", "closeDate", "owner"].