Building & Editing Views with Aero
Last updated: June 16, 2026
Views are one of the most powerful ways to slice your onboarding data in OnRamp — but configuring filters, columns, and grouping from scratch takes time. Aero, OnRamp's AI assistant, can build and edit Views for you through a simple conversation.
New to Views? Start with to learn what Views are and how to use them manually. This article covers what Aero can do on top of that.
What Aero Can Do with Views
When you open Aero and ask a data question, Aero doesn't immediately build a View. It answers your question in the most useful way first — and then offers to save it. Here's how it works:
Aero routes your question to the right surface. Before creating anything, Aero checks three places:
Do you already have a View that answers this question? If so, Aero links you to it.
Does an Insights chart cover this? If so, Aero links you there.
If neither applies, Aero answers the question directly in chat.
After answering, Aero offers to save it as a new View if the question is a good fit for one.
Aero can create a new View from a plain-language description. You don't need to know which object type to use or which filters exist. Just describe what you want to see, and Aero figures out the configuration.
Aero can edit a View you're already looking at. When you're on an existing View, you can ask Aero to add a filter, change the sort order, swap out columns, or adjust grouping — all without touching the settings yourself.
Creating a New View
You can ask Aero to create a View at any time. Some examples of how to phrase it:
"Create a view of all overdue projects assigned to me"
"Make me a new view of tasks grouped by owner and status"
How the flow works:
Step 1 — Aero proposes a plan. Aero describes the View it intends to build: the object type (Projects, Tasks, Subtasks, etc.), filters, columns, grouping, and sort order. It will ask if you want to proceed, and surface chips to confirm, adjust, or cancel.
If a similar View already exists, Aero will flag it and ask whether you'd like to use the existing one, clone it as a starting point, or create a new one from scratch.
Step 2 — Approve or adjust. Tap Approve Draft to build the View, Change to refine the plan, or Reject to cancel. If you want to adjust something — different columns, a different filter — tap Change and Aero will ask what to update.
Step 3 — Review the draft. Once you approve, Aero builds a draft version of the View and opens it for you to review. The View is not live yet — you can see exactly what it will look like before committing.
Step 4 — Apply or discard. Tap Apply view to make it live, Change to keep refining, or Discard to remove the draft entirely.
Editing a View You're Already On
When you're viewing an existing View, Aero can modify it directly without going through a draft. Just describe the change you want:
"Add a filter for overdue only"
"Sort by due date instead"
"Remove the owner column"
"Change the grouping to status, then owner"
How the flow works:
Step 1 — Aero confirms the change. Aero shows you the current View configuration and the specific change it's about to make. Tap Yes, Update to proceed.
Step 2 — The change is applied. Aero writes the change directly to the live View. There's no draft step for edits — changes go live immediately after you confirm.
If you're already reviewing a draft View (one Aero built but you haven't applied yet), Aero will edit the draft rather than the live View.
What Aero Can Configure
When creating or editing a View, Aero can set:
Setting | What it controls |
|---|---|
Object type | What the View shows — Projects, Tasks, Subtasks, and more |
Filters | Conditions that limit which records appear (e.g. status, due date, owner, overdue flag) |
Columns | Which fields are displayed for each record |
Grouping | Up to three levels of nested grouping (e.g. group by status, then by owner) |
Sort order | A single field and direction (ascending or descending) |
Name and description | What the View is called and an optional summary |
When Aero Can't Build a View
Some data questions involve fields or aggregations that Views don't support. When this happens, Aero will:
Answer the question inline in chat anyway (so you're never left empty-handed)
Explain what the limitation is in plain language
If a close substitute field exists — for example, a View can filter on planned start date but not actual start date — Aero will name the difference and offer to save a View using the substitute, so you can decide.
Tips
You don't need to be on a Views page to get started. Open Aero from anywhere and describe what you want to understand about your onboarding work. Aero will determine the right object type and configuration.
Ask data questions first. If you're not sure whether a View is the right tool, just ask the question. Aero will answer it and then offer to save it as a View if it makes sense.
Aero tracks the View you're on. When you're viewing a specific View, Aero uses it as context — so "add a filter for this month" applies to the View you're looking at, not a new one.
Aero only edits what you ask it to. When modifying an existing View, Aero merges changes in rather than replacing the whole configuration — your existing filters, columns, and grouping are preserved unless you ask to change them.