Build and edit with Hugo

Create with Hugo and the in-page Hugo launcher open a builder beside the work. Hugo can create or change records while replying. Watch the page, then check the saved result. This differs from Ask Hugo for product help, which explains documentation and opens pages.

Follow live changesCopy Anchor Link

1. Select the correct site and open the area you want to work in.
2. Choose Create with Hugo where offered, or open Hugo on an existing editable record. Some builders first ask what to create; once a record exists, Bulk opens it with Hugo still beside it.
3. Describe the outcome, the records and any limits. Answer Hugo's follow-up questions. For example, name the project, reporting period or worksheet instead of relying on an ambiguous “this one”.
4. Watch the activity bar: Hugo is thinking, then actions such as Adding, Updating or Removing a named item. Changed rows/widgets are highlighted and the page can follow the current item.
5. Wait for the reply to finish, inspect the change summary and review the actual fields. A draft, table or layout can already be saved before you receive the final reply.

Do not wait for a universal Apply button. The current builders write through the page's normal rules and permissions. Creating a task or changing a shared board can therefore affect other people immediately. A request that only asks for advice should say so clearly; inspect the page before treating a response as advice only.

Uploads use the file types and limits shown by that builder. The shared import can take up to three files at a time. PDF/photo intake can help recreate an audit, assessment, task, report or print template. KPI/export panels also offer CSV-style source files. The datasheet builder works from the open workbook and does not offer that document-import row.

Undo an eligible replyCopy Anchor Link

After an eligible reply completes, the activity bar shows its change summary and Undo. Select Undo to reverse that reply's recorded changes, then review the page. It is a whole-reply operation, not a button to undo one highlighted field.

• Wait while Hugo is working. Undo is for the latest eligible change on that subject, with current access checks.
• Use Undo before further manual edits. Some builders refuse reversal when the record has since changed; others restore a copy of the earlier values. Do not assume every later manual edit will be protected. Read any error and check the resulting fields.
• Undo has domain-specific limits. For example, the first task opened when starting with Hugo remains, while additional tasks/subtasks may be removed; see its guide. Reversing a record change does not recall an email or an already generated file.
• Dismiss hides the summary without reversing anything. Closing Hugo also leaves saved changes in place.
• New chat starts another conversation. It does not reset the record or undo the previous conversation's work.

If a response errors after visible changes have landed, inspect what is saved. Do not assume an error rolled back every earlier step. Use Undo when offered, or correct the record through its normal editor.

Choose the right builderCopy Anchor Link

Permissions and confirmationCopy Anchor Link

Hugo needs chat.use and the owning feature's access. Opening a panel does not grant permission for every action it can describe. Record/site restrictions remain in force. Each linked guide explains the main write permission and the state in which editing is allowed.

Export runs and delivery/schedule actions appear as review cards. Report generation and delivery/schedule actions also use cards. Check the selected template, filters or period, recipients and schedule, then use the card's named button, such as Run export, Generate or Create schedule, or Cancel. Nothing starts merely because that card appeared. A completed card records its outcome when you reopen the chat.

This confirmation rule is specific to those actions. Builder edits can save directly, and an authorized request to publish a report or PDF template can publish it through Hugo. Review the draft and preview before asking for publication; do not assume every save or publish request will produce another approval card.

A general assistant conversation may still show proposal cards with Apply or Create. Follow the controls on that card. Those older/general-chat flows do not describe how the current in-page builders save their changes.

If the builder is missing or stopsCopy Anchor Link

Check the selected site, your chat and feature permissions, and the record's editable state. A published audit template or non-Draft datasheet does not become editable because Hugo is open. Resolve an unsaved local change or save failure before asking Hugo to rewrite the same content. If AI is unavailable, use the normal editor; saved work remains subject to its normal state and access rules.