Getting Started with Aeion Views

Navigate to any collection in the Aeion admin. Try CRM → Deals, Commerce → Orders, or Helpdesk → Tickets.

1. Click Add Filter in the collection toolbar
2. Add your first condition — e.g., Stage equals "Negotiation"
3. Add another — e.g., Close Date is before July 1, 2026
4. Set a sort — click the sort icon, e.g., Value ↓ (highest value first)
5. Toggle some columns off — click the column selector, uncheck fields you don't need
6. Reorder columns — drag the column headers to change the order

Your filter bar now shows: Stage = Negotiation AND Close Date < 2026-07-01, sorted by Value descending.

The data changes to match your configuration. This is your "working state" — it's applied but not yet saved.

With your filter configured, click the Saved Views bookmark icon in the collection toolbar (it looks like []).

1. Click "Save Current View" (or "Save as..." depending on state)
2. Enter a name: Q2 Negotiation Deals
3. The view saves to your account with your current configuration:

The view now appears in the dropdown under your name. Click it to instantly reapply those settings. All 5 configurations apply at once.

Saved view appears in dropdown:

``` My Views ★ Q2 Negotiation Deals ← click to apply ✎ Deals I Own ← rename ✎ High-Value Leads ← rename

Shared With Me ★ Pipeline Overview ← shared by admin

Default View ← system default ─── Apply All Filters ─── ← resets to default ```

Click the Saved Views bookmark icon. Next to your saved view, toggle the Share switch.

What changes:

• Your view is marked as shared
• The view now appears in the "Shared With Me" section for every user in your tenant
• They can apply it, but cannot rename or delete it (read-only for non-owners)
• The original owner (you) retains full edit/delete access

Team perspective: When your colleague opens the Deals collection and clicks Saved Views, they see:

• Their own saved views
• "Q2 Negotiation Deals" under "Shared With Me" (from you)

Admin sharing: Admins can share a view as a "tenant-wide standard" — every new user sees it as the default view for that collection.

From the Saved Views dropdown, click the star icon next to any view.

What happens:

1. Aeion marks this view as your default for the Deals collection
2. Your previous default (if any) is automatically unset in the same step — you never end up with two defaults
3. Next time you open the Deals collection, this view loads automatically

Multiple defaults: You can have one default per collection per user:

• Deals → "My Pipeline"
• Orders → "Today's Orders"
• Tickets → "My Open Tickets"
• Inventory → "Low Stock Items"

Each collection remembers its own default independently.

Saved views store the viewType field. Try switching for the same data:

List View — Best for detailed data, many columns, bulk editing

Kanban Board — Best for stages, statuses, pipeline flows

• Click the view switcher (top-right of collection toolbar)
• Select Kanban
• The view groups by your chosen field (e.g., deal Stage, order Status, ticket Priority)
• Save this as a new view: Deals Pipeline (Kanban)

Calendar View — Best for dates, schedules, deadlines

• Select Calendar
• Choose the date field (e.g., Close Date, Due Date, Start Date)
• Records appear on their due dates
• Drag to reschedule (if permissions allow)

Gallery View — Best for image-heavy collections

• Select Gallery
• Records display as cards with image thumbnails
• Works with Media, Products, Real Estate, etc.

Gantt View — Best for timelines, projects, scheduling

• Select Gantt
• Records display as bars on a timeline
• Useful for Production shoot schedules, Construction projects, SCM deliveries

Save each view type as a separate saved view. Switch between them freely.

Beyond simple equality, Aeion's QueryBuilder supports rich filter conditions.

Relative dates — Use the newer_than / older_than operators with a duration string (30d, 2w, 6h) to make views always-current without hardcoded dates:

json { "lastActivity": { "newer_than": "7d" } }

View name: Active This Week — the comparison is evaluated against the current time every time the view runs, so it never needs editing.

Filtering to "your own" records — Saved-view filters store literal values, not per-viewer template tokens — there's no placeholder that resolves to "whoever is looking" today. For a personal filter, use your own literal user ID:

json { "owner": { "equals": "usr_01J8XK4..." } }

View name: My Deals — this is a personal, unshared view; if a teammate applies it, they'd see your deals, not theirs, so don't mark it shared.

OR conditions — Match either of two criteria:

json { "or": [{ "value": { "gte": 100000 } }, { "priority": { "equals": "high" } }] }

View name: Enterprise Deals or High Priority — large deals or urgent items.

Array contains — Match records with a tag or category:

json { "tags": { "contains": "enterprise" } }

View name: Enterprise Accounts

Not-in conditions — Exclude values:

json { "status": { "not_in": ["Closed Won", "Closed Lost", "Archived"] } }

View name: Active Pipeline Only

A saved view can carry a conditionalFormatting field — rules that would color-code records based on field values, saved right alongside the view's filter, sort, and columns:

json POST /views { "name": "High-Value Pipeline with Risk Flags", "collectionSlug": "deals", "filter": { "stage": { "equals": "Negotiation" } }, "conditionalFormatting": [ { "field": "value", "op": "gte", "value": 100000, "style": { "badge": "green" } }, { "field": "status", "op": "equals", "value": "at_risk", "style": { "badge": "red" } } ] }

Heads up: the collection list view doesn't render these rules yet — there's no in-toolbar "Format" button today, and the rules you save won't visibly change badges or row colors. The field exists on the saved view so a config you write now is preserved forward-compatibly; treat it as API-only plumbing rather than a shipped list-view feature until it's wired up.