
Use **AI Insights** when you want a widget to explain its current data in plain language.

This is different from the dashboard-level assistant. Dashboard AI Assistant works across the whole dashboard. **AI Insights** stays focused on the widget you are editing.

## Open AI Insights

1. Open a dashboard.
2. Open or create a **Data Research** widget.
3. Click the widget's **AI Insights** icon.

This opens AI Insights for that widget, using the current widget preview as the context for the answer.

![AI Insights entry point on a widget](/docs/ai-assistance/widget-ai-assist/01-widget-ai-insights-entry.png)

## What AI Insights does

AI Insights uses the current widget preview as context and helps you:

- summarize what the widget is showing
- identify trends
- call out anomalies
- compare visible values
- explain the result in a format that is easier to share

Because it works from the current widget preview, the answer stays tied to that widget instead of the whole dashboard.

## View AI Insights

![AI Insights answer for the selected widget](/docs/ai-assistance/widget-ai-assist/02-widget-ai-insights-answer.png)

## Configure the question and answer style

Use the question and style settings to shape how the answer should read before you generate it.

![AI Insights panel in the widget editor](/docs/ai-assistance/widget-ai-assist/03-widget-ai-insights-panel.png)

## Choose a starting prompt

The panel suggests useful starting prompts such as:

- summarize key insights
- identify trends
- identify anomalies

Use one of these when you want a quick starting point, or write your own question when you need a more specific result.

## Pick an answer style

Before you generate the answer, you can choose how the result should be presented.

Depending on what you need, you can turn on options such as:

- emojis
- table output
- shorter wording
- bullet points
- comparisons
- color references
- drill down

These options change how the answer is written. They do not change the widget data itself.

## Ask a focused question

Good questions stay close to what the widget is showing.

For example:

- summarize this widget
- compare the top values
- explain the largest difference
- identify anything unusual
- highlight the most important takeaway

If the answer is too broad, ask again with a narrower comparison or a clearer outcome.

![AI Insights question and answer style options](/docs/ai-assistance/widget-ai-assist/04-widget-ai-insights-question.png)

## Tips

- Use AI Insights after the widget preview looks close to final.
- Ask about one result, trend, or comparison at a time.
- Use answer style chips when the response needs to be easier to scan.
- Adjust the widget setup first if the preview does not show the data you want explained.

## Read next

- [Dashboard AI Assistant](/docs/ai-assistance/dashboard-ai-assistant) - Ask about or revise the whole dashboard.
- [Data Research Widgets](/docs/dashboards/data-research-widgets) - Full widget setup guide.


Use AI Insights inside a data research widget to ask questions about the current preview, choose an answer style, and generate a plain-language explanation.

AI Insights


Use **Preferences** to choose how Zira works for you.

For example, you can change the color theme, notification sound, date format, and the page that opens first after you sign in.

## Open Preferences

1. Look for your profile picture in the top-right app area.
2. Click your profile picture.
3. Select **Preferences**.

## Change the options you want

Inside **Preferences**, you can update options such as:

- **Theme**
- **Notifications Tone**
- **Date and time format**
- **Home Page**

Take your time and change only the options you want.

![Preferences window with Theme, Notifications Tone, Date and time format, and Home Page visible.](/docs/getting-started/profile-preferences/preferences/02-preferences-window.png)

## Save your changes

1. Review the updated options.
2. Click **Save**.

If you change your mind before saving, click **Cancel**.

## Home Page tip

The **Home Page** setting chooses what opens first after you sign in.

For step-by-step help, see **Choose Your Home Page**.

If your team uses it, you may also see **Open AI Home Builder**, which helps you create a more personalized home page.

## Related guides

- [Choose Your Home Page](/docs/getting-started/profile-preferences/home-page) - Set a dashboard or another page to open first.
- [Update Your Profile](/docs/getting-started/profile-preferences/profile) - Change your photo, personal details, and signature.
- [Change Your Password](/docs/getting-started/account-access/change-password) - Update your password when needed.


Choose how Zira looks, sounds, and opens for your personal account.

Change Your Preferences


A trim saw camera measures how long a board is before the saw and how long it is after. To do that
it has to know where the saw's **stops** are and what size cut each one makes.

**Trim saw stops** is where you teach it, from the console. Open it beside the live view, let the saw
run, and the camera works the positions out for itself while you watch.

## Open the panel

Open the data source, go to **Remote Control**, and choose **Trim saw stops** from the rail on the
right. The live view starts on its own, and the panel opens next to it rather than over it — a
collection runs for minutes, and you need to watch the boards while it does.

## What a calibration actually is

Two things make up a stop: **where it is**, and **what size it cuts**.

- **Where it is** is measured by the camera. You never enter it, and you cannot nudge it from here.
- **What size it cuts** is the part only you know, so that is the only thing the panel asks you for.

The scale comes from the distance between two different cuts, which is why a camera normally needs
**at least two sizes** before it can measure anything.

## Start a run

Press **Collect**. A setup window opens and asks two things before anything goes to the camera.

**Which side of the board the stops are on.** Pick from the sides the camera offers — **Left**,
**Right**, **Top** or **Bottom**. The list is the camera's own, based on how it is mounted, and it
decides how every board in the run is measured. Pick the side the boards are trimmed from.

**Expected cut sizes**, which are optional. Type the sizes the saw cuts, separated by commas —
`30, 34, 38`. Leave it empty and you label each captured line afterwards instead. Both work; declare
them up front when you already know them, and the panel can warn you about a size that will not
separate cleanly from one the camera already has.

Then press the button to begin.

### If the camera already has stops

A camera that has been calibrated before asks first what this run is for:

- **Keep them and re-measure** — the existing stops keep their sizes. Use this for a saw that has
  drifted, or to add a cut well clear of the ones already set up.
- **Remove them and start over** — forget the calibration first, then collect every cut from
  scratch.

Choosing to start over turns the window into a single confirmation naming how many stops will go.
**The run does not begin by itself afterwards** — watch the applied count drop to zero, then press
**Collect** again. Throwing away a working calibration and starting a new run should not be one
gesture.

Adding one extra size to an already-calibrated saw is the case that catches people out. The camera
matches each new line against the stops it already approved, so a new cut close to an existing one
gets absorbed by it and the run is refused. If a size you typed is going to land too close, the setup
window names it before you start.

### Cameras set up for one cut size

A camera commissioned against a measured reference already has the scale that two sizes would
otherwise provide, so it can be calibrated from **a single cut**. When that applies the window says
so and shows the reference it was given. It is read-only — that reference is entered at the camera,
not from here.

## While it runs

Let the saw work. Each stop the camera finds appears as a captured line, and the panel reports what
it is doing as it goes.

When you have enough, press **Stop**. Then:

1. **Label each line** with the size it cuts. The lines are lettered to match the letters drawn on
   the live video, so you can see which line is which.
2. **Drop any line that is not a real stop** — a stray reading, or something that went past that was
   not a cut.
3. Press **Apply**.

The panel counts labelled lines as you go, so you can see how many are still waiting.

## A run stays open until you close it

Nothing times a collection out. If you close the panel, switch tab, or refresh, the camera carries on
collecting with nothing on screen to say so — and the next **Collect** is refused because a run is
already going.

So a **chip in the data source toolbar** stays visible while a run is unfinished, including one
stopped but never applied, and including a run somebody started at the machine rather than from here.
Open the panel again and either finish the run or cancel it.

## Read next

- [Remote Control](/docs/ai-vision/remote-control) — the rest of the tab: live view, recording, image sampling and device settings.
- [Overview](/docs/ai-vision/overview) — the AI Vision workspace.


Calibrate a trim saw from the console — collect its cut positions by watching boards go past on the live view, label each one with the size it cuts, and apply.

Browse Guides

AI Insights

Open AI Insights

What AI Insights does

View AI Insights

Configure the question and answer style

Choose a starting prompt

Pick an answer style

Ask a focused question

Tips

Read next