What Aero can edit in a project

The short version

Aero can change live project and task data for you — reassigning tasks, moving dates, renaming things, updating project settings and data fields, and adding comments. It can do this to one record or to hundreds at once.

Aero never changes anything on its own. It proposes the change, you review it on a card in the chat, and clicking Apply changes is what makes it happen. Telling Aero “yes, go ahead” in the chat does not approve anything — only the button does.

When a change is applied, it runs with your permissions, and behaves exactly like the same edit made by hand.

Where to ask Aero about project changes

Open it with the Ask Aero button in the top right of the page. It opens as a floating panel, and you can dock it to the left or right. This is where everything in the rest of this article happens.

Just describe what you want in your own words. See Example requests below for phrasings that work well.

How the chat works

1. You ask. “Reassign all of Ben’s overdue tasks to Shawn.” “Push the Acme go-live to March 1.”

2. Aero finds the records. It works out exactly which tasks or projects you mean. If your request matches more than one thing, it asks which you meant rather than guessing.

3. Aero proposes. A card appears in the chat listing every affected record, its current value, and the new value. A banner reads: “Nothing has changed yet — review the proposed changes and choose Apply or Decline.”

4. You approve or decline. Nothing is written until you click Apply changes.

Want a narrower set? Just say so — “only the Acme ones” — and Aero proposes again. The new card replaces the old one.

While a card is open, sending another message won’t get past it: Aero replies “Choose an option on the card above before sending another message.”

What you can change from the chat

On tasks

Assignee and task type can’t be changed on completed tasks. Aero only sees tasks on live projects.

On projects

Project data fields

Aero can set any project data field — name the field and the value you want. For a dropdown or multi-select, give the option exactly as it’s stored. You also need permission to edit that particular field.

Comments

Aero can add a comment to a task, reply to an existing comment, and edit a comment’s text.

• Comments are internal unless you ask for a customer-visible one. “Add a comment to these tasks” produces internal comments. Aero states the audience for every comment it proposes, and the card repeats it per record.

• A comment on an internal task stays internal no matter what, because the customer can’t see the task in the first place.

• A customer-visible comment appears in the customer’s portal the moment it’s applied, and can never be unshared or deleted.

• You can only edit your own comments, and a comment containing @mentions or formatting can’t be edited here at all, because editing would strip them.

• If a project has comments turned off, those records are refused.

• None of the three can be undone. A comment can’t be deleted, and editing one can’t recall the notifications it already sent.

What the chat can’t change

The list above is the complete set. Anything else, Aero will tell you it can’t do and point you to where it can be done instead. That includes:

• Task status — the chat can’t complete or reopen a task. (The Recommended Actions card can mark a task complete — see below.)

• Tags and task descriptions

• Project notes

• Modules and stages, resources, contacts, and project membership

• Task data fields (project data fields only)

• Anything on an archived or deleted project or task

Aero also cannot create or delete records from the chat. It changes attributes on things that already exist. The one exception is comments, which it can add.

The approval card

The card is the whole safety mechanism, so it’s worth knowing what it shows.

• A one-line summary of what’s changing and how much — for example, “Assignee on 12 tasks across 3 projects.”

• Every affected record, with the current value struck through and the new value beside it. Past four records, a View all link opens the full list with a search box.

• A checkbox per record, so you can drop individual ones before applying.

• Excluded records, with reasons — for example, “3 excluded — 2 you can’t edit, 1 changed since the preview.”

• A standing warning that can’t be dismissed: “These changes trigger the same email notifications and automations as a manual edit, per each project’s configuration.”

• An extra warning whenever a customer-visible comment is involved, spelling out that it can’t be unshared or deleted.

• Decline and Apply changes buttons. If some records fail, a Retry button appears.

A proposal expires after 10 minutes. If it expires, or if someone else edits those records in the meantime, Aero will ask you to re-propose — that’s deliberate, so you never approve a preview that’s gone stale.

Applied changes show up in the project’s activity feed under your name, tagged via Aero. Aero is never the actor; you are.

Side effects: approved changes are real edits

This is the most important thing to understand. An approved change is not a quiet background update. It behaves exactly like the same edit made by hand, which means automations, notifications, emails, and webhooks configured on those projects will fire.

If you’re reassigning 80 tasks, 80 assignment notifications go out. Aero says this before you approve, and the card repeats it. Consider turning off email on the affected projects first if that’s not what you want.

Reviewing and undoing changes

Ask “what did you change?” and Aero lists your recent applied changes — what changed, how many records, and when. It keeps the last 10 to hand, and change history is retained for 90 days.

Ask “undo that” and Aero proposes the reversal. The undo is itself a change set with its own approval card, and it fires the same notifications going back as it did going forward. Records that someone else has changed since the original run are excluded and shown with a reason.

Only the person who made a change can undo it through Aero. A teammate or OnRamp support can’t undo it on your behalf — they’d have to make the reverse edit manually.

What can’t be undone: task type changes, and all three comment actions. Everything else can.

Undo keeps working even if Aero editing is switched off for your organization — it’s deliberately the one thing that stays available.

Limits

Go over a cap and the proposal is refused. Aero will offer to split the work — by project, owner, or date range — and start with the first batch.

Each change set covers one attribute with one new value. Changing two different things means two proposals.

Who can use it

Aero is available to Super Admins, Creators, & Integrators.. Collaborators, Contributors, and API users can’t use it. Portal users can never drive internal edits.

Within that, Aero can only change what you could change yourself. Permissions are checked record by record at the moment the change is written, so a record you don’t have rights to is skipped and shown on the card with a reason.

Example requests

• “Reassign all of Ben’s overdue tasks to Shawn.”

• “Rename those tasks to Kickoff call.”

• “Push the Acme go-live to March 1.”

• “Make Sarah the owner of every project going live this quarter.”

• “Turn off customer emails on these projects.”

• “Make these tasks customer-facing.”

• “Add a comment to each of these tasks saying the kickoff moved.”

• “Show me everything you changed today.”

• “Undo that.”

You can also chain off a question. Ask “show me overdue tasks” first, then say “reassign those to Shawn” — Aero reuses the exact set it just showed you.