Explores
How notebooks, conversations, saved work, sharing, and continuation fit together.
An Explore keeps a notebook and its associated conversations together, so you can return to an analysis, check how a result was made, and build on it.
Explore, notebook and board
The notebook contains cells and their layout. Cells hold the queries, calculations and outputs; the layout arranges selected outputs as a board. A board presents work from the same Explore. Switching between Notebook and Layout does not create another analysis. See Notebooks for cells, dependencies and layout behavior.
Conversations let you ask questions and follow-ups about that work. Which messages are kept depends on whether you are editing the Explore or viewing it.
Edit and View
| Surface | What you can do |
|---|---|
| Edit | Develop the analysis with the agent, author cells and arrange the layout. Notebook changes and the editing conversation are saved to the Explore. |
| View | Read the board or notebook, interact with controls and use Ask for follow-ups. A live View session can run existing cells, but cannot change the source Explore's cells or title. |
The Hybrid and Notebook view presets change how much notebook detail you see. They do not grant editing access or make a copy.
View chat starts separately from the saved editing conversation. Its messages belong to that live View session and are not saved to the source Explore. To keep a View discussion as editable work, continue in a new Explore.
Saved work and live execution
Saved notebook work includes cell source, configuration, layout and stored outputs. Editing sessions also save their conversation history. A live session holds the running notebook and its current execution state; reopening saved work does not preserve that running process.
A displayed output may come from an earlier run. For example, editing a query can leave its previous result visible until the cell runs again. Check the execution result before using an answer after changing code, data or context. See Execution and sessions for the lifecycle.
Sharing and access
The creator receives Full access to a new Explore. Workspace settings set its initial visibility to Private, Workspace can view or Workspace can edit. You can also grant access to individual workspace users or Everyone in workspace.
| Explore access | Included actions |
|---|---|
| View | Read the Explore. |
| Edit | Read and edit it. Sharing and deletion are not included. |
| Full access | Edit, share and delete it. |
A workspace link opens the saved Explore; copying the link does not grant access. Effective grants can also come from workspace roles or other policies, so a person's listed grant may not describe all their access.
Reading saved results does not grant query access. Running a query requires datasource permission and exactly one distinct authorized credential, even for an Admin. See Users, roles and groups.
A public web link lets anyone with the link read the saved Explore, including its cells, outputs and editing conversation. Hiding a cell from the board does not hide it from the public content. The public page does not run queries or offer Ask. Revoking the public link leaves workspace grants in place. Follow Share an Explore or board to review and publish content.
Duplicate and continue
Both actions create an independent Explore. Later changes in the copy do not synchronize with the source.
| Action | What the new Explore contains | Access on the copy |
|---|---|---|
| Duplicate | The saved notebook, stored outputs and saved editing conversation. | The new creator has access; current workspace default visibility applies. The source sharing list is not copied. |
| Continue in a new explore | Cells tagged in the live View session, their upstream dependencies, available outputs and the current View chat. The source editing conversation and unrelated cells are excluded. | The new creator has access. Workspace default sharing and the source sharing list are not copied; other effective grants can still apply. |
Continuation is also called Explore from here. A cell tagged in an unsent draft is selected, but the draft text is not copied. Send a message first if you want it in the new conversation. The action waits while the agent is replying and requires permission to duplicate the source and access to your own live session.
For example, tagging a chart that uses a calculated total from a query includes the chart, total and query cells. It leaves an unrelated chart behind. Continuation retains the included cells' source, configuration and layout. It captures the live selection without overwriting the source.
Both copy actions retain the source datasource selection but grant no new query permission. Neither action runs the copied cells; check stored outputs against a new execution when you use the copy. Follow Explore from a board for the continuation steps, or Find and organize saved work to return to an Explore. Share a copy separately when it is ready.
For a focused follow-up, see Ask one checkable question.
To inspect or change the model, see Check data and model selection. Available models depend on your deployment and plan.
Limits and failures
| Condition | What happens |
|---|---|
| Another editor is connected | Already open for editing. Use View and retry when the other editor finishes. |
| An automation is using the Explore | Automation using this explore. Retry editing after the run finishes. |
| Continuation has active execution | The copy is refused until the live session finishes. Wait, then retry. |
| A tagged cell is missing or notebook syntax blocks dependency resolution | Continuation fails. Check the selected cells and fix syntax errors before retrying. |
| The live session expired | Continuation cannot use it. Reopen the Explore and establish a current selection. |
Last updated on October 27, 2026