Organize work into reports and pages

A report is the shared container for your analysis. It holds connections, pages, visuals, instructions, reference files, access settings, and associated conversations.

Each report can mix Report Pages, which use Unity's native canvas, and HTML Pages, which use custom layouts with registered live visuals.

Create a report

1. Open Reports and click Create New Report.
2. Enter a Report Name.
3. Review the ownership message, then click Create Report.
4. Attach data and add pages for the questions you want to answer.

If you belong to an active organization, the new report belongs to that organization and stays private until shared. Without an organization, it is personal. Joining an organization later does not automatically migrate existing personal reports.

Choose a page type

Both types use the same report's access, attached connections, instructions, and reference files. The assistant can inspect and edit either from the same conversation.

Create an HTML executive overview and a native detail page in this
report. Reuse the same model definitions and explain the purpose
of each page.

Manage pages

The page list groups native and HTML pages separately. Expand or collapse a group, select a page, or use New report page and New HTML page. The address names the open page, so a link or a reload reopens it, and the browser's Back and Forward move between the pages you opened.

Hover a page and select More actions (…) for Share page…, Duplicate, Rename, and Delete, subject to your access; hover a cut-off name to read it in full. Rename changes the page's name (Enter saves). A native page's width, height and backgrounds are set in Page settings on its canvas.

Duplicating a page provides a starting point with copied content. Review its queries, filters, and visibility before treating the copy as a different analytical scope. An invisible page stays invisible when duplicated.

The assistant can create, update, duplicate, and delete pages through recorded operations. Name the page explicitly when the report contains similar content.

Edit together

Several people can work in one report at once. How much they share a page depends on its type.

• Report pages. Everyone who can edit the page edits it at the same time, and you see each other's changes as they happen. A small name tag and an outline show what other people are doing: "Selected by Dana" on a chart she has selected, "Dana is editing" while she drags or resizes it or has unsaved changes in its settings, and "Assistant for Dana is editing" while her assistant changes it. Selecting a chart, even with its settings open, does not protect it: it is protected only while the person is working in the settings. While a chart is being edited it is hers: if you try to change it you are told who ("Dana is editing this chart.") at the chart and nothing is saved. The rest of the page stays editable. The chart is free again about ten seconds after the activity stops, or ten seconds after the assistant's change finishes, and never stays reserved for more than five minutes without a saved change. A report Admin or Owner can end someone else's hold on a chart. Your own assistant can change a chart you are editing.
• HTML pages. An HTML page is one document, so one person edits it at a time. There is no Edit button: your first change starts your editing session, you see "You're editing", and everyone else sees "Dana is editing". The session ends when you leave the page, after 45 seconds with no change and no focus on the tab (working inside the page counts as focus), or after ten minutes without a change. Saving from the Source dialog is a change and starts your session. Someone who needs the page can choose Request to edit; you see a prompt, and if you do not answer within 30 seconds the page passes to them. Report Admins and Owners can take it at once.
• Not saved. A change that someone else's editing refused is never dropped silently. It stays on screen as "Not saved" with the reason. When the chart or page is free, choose Save again to send the same change, or Dismiss to let it go. Nothing is sent without your choice. Save again is checked against the version you made the change on: if the page or chart changed since, it is refused, so it never overwrites the other person's work by itself. A chart edit made after someone else changed the chart (your text box's text, a setting) is kept the same way, with your text shown: choose Apply mine to replace their change with yours. An HTML page change is reapplied by hand in Source. Only a move, a resize or a delete replaces what the other person did to the chart, and the notice says so. The list shows only your own changes on the page you have open.
• Page-wide actions. Deleting a report page or restoring an earlier version is refused while another person is editing one of its charts (it names the person: "Dana is editing a chart on this page. Try again in a moment.").
• Who is here. A row of initials beside the page tools shows who else is on the page, and hovering one tells what they have selected or are editing. This is shown only to people who can open the page. It is never shown on a public link and the assistant does not see it.
• Automations. A call through an API key or MCP holds what it changes only while it runs, so it never leaves a page marked as being edited, and it cannot ask to hold a page or chart for longer. Where someone else is editing, it is refused with the same message.

Understand the hierarchy

A dashboard can be one page within a larger report. Multiple pages do not require multiple reports or separate copies of the reference files.

Arrange native pages

Move and resize objects on the canvas. A native page has a saved logical width and height, defaulting to 1,280 × 720. Browser size, panel resizing, zoom, and adding visuals do not change those dimensions. Only an explicit page-size edit by a person or the assistant changes them. Objects outside the boundary can be clipped.

HTML pages use their authored responsive HTML/CSS layout and can scroll. The native page-size rule does not impose a fixed canvas on an HTML page.

Layout and appearance remain editable after AI creation. The assistant can inspect saved positions and supported properties, but you should still review label wrapping, overlap, and readability.

See Native visuals and Workspace controls.

Build HTML pages

An HTML page composes independently registered live visuals through a custom layout. Each component retains its dataset/query context and inspection controls.

The assistant can build the entire page, check query and renderer feedback, inspect a browser screenshot, and repair problems. Manual Source, Adjust, Refresh live data, and Version history controls remain available.

See HTML pages.

Present and explore

Use Preview page for the viewing experience: the page alone, without the app header or panel. Move the pointer to the top edge of the screen for the Report page picker, which moves between native and HTML pages, and Edit. Press Esc to return to editing.

Presentation mode is a workspace control. It does not change another person's authorization. Use Sharing and access and Page visibility to control access.

Change or remove a report

The report list provides Manage Access, Rename, and Delete according to your role. Deleting a report is broader than deleting a page or clearing a filter: it removes the report's workspace. A CSV connection imported for the report is deleted with it unless another report uses it.

Organization ownership, human report ownership, and team access are separate. See Report ownership before transferring responsibility or offboarding a member.