Google announced interactive-site generation in Gemini Notebook on November 16, starting from sources and notes added by the user. The company presents examples of visual explainers, sales dashboards and project-tracking tools. The feature is rolling out globally on the web for users aged 18 and over, including Google Workspace users, according to the announcement describing its availability.

Support in the mobile app is announced for a later stage. The availability described now therefore concerns the web interface, with a gradual rollout rather than a simultaneous release across every product interface. Google's documentation adds rules covering generation, notebook access, data entered in the site and sharing of the resulting materials to the initial product announcement.

Team examining documents and charts on paper and a tablet
Mikael Blomkvist

Notebook sources become the starting point for an interface

The feature's idea is to turn information in a notebook into a presentation with interactive elements. Instead of an exclusively linear answer, the user can obtain an interface adapted to the subject described. Google's examples show visual organization of information and controls for exploring it, within the resources available in the notebook being used for generation.

Generation starts in the notebook conversation with a description of the desired site. The process runs in the background, allowing the user to continue working while the result is prepared. The generated site appears in the Studio area and can be opened separately in a new tab to occupy the full area of the browser window.

This workflow concerns a Google product feature and the sources loaded into the notebook. A dashboard example does not, by itself, announce an automatic connection to a company's accounting or customer database. Available data, the instructions given and documented functions establish the generated material's context, including the context of the examples presented by the company.

Data entered into controls are saved for each user

The documentation describes retaining selections, checked boxes, notes and text entered into the site. On reopening it, a user can find their own data and options again. This persistence allows continued use of the interface rather than returning each time to a version without the selections and observations previously entered by that particular person.

On a shared site, these inputs are private to each user. According to Google, even the site owner cannot see what other people enter into their controls. This is an essential rule for interpreting project-tracking examples: a personal check mark and a shared project status have different behaviors, even if their visual presentation appears similar.

For a team, two information levels matter: the notebook sources, consulted according to access permissions, and data each person enters into the site. Google's documentation specifies that the second level remains individual. A shared interface appearance does not change this rule governing the retention of personal notes and selections entered by each person using the site.

What the functions described by Google allow

ElementDocumented behaviorAccess condition
Generating a siteStarts in conversation; the result appears in StudioNotebook editing access
Notes and selectionsRetained for the person entering themNot visible to other users of the site
Opening a shared siteLinked to notebook accessFull notebook access, according to documentation
DownloadingThe site file can be downloadedThe option alone does not define format or functionality

From sources to interactive exploration

  1. Sources
    Notebook documents and notes
  2. Generation
    Describe the interface in conversation
  3. Site in Studio
    Visual explanations and interactive controls
  4. Personal inputs
    Notes and selections private to each user

Sharing depends on notebook permissions

Generating and deleting a site require notebook editing access. To open a shared site, the recipient needs full notebook access, according to the documentation. A link to the resulting interface therefore does not represent a separate permission system that automatically isolates the site from access to the materials contained in the notebook used to generate it.

The rules for public sharing and managing access require a personal account and owner or editor status. This scope needs to be separated from the availability of generation for Workspace users. Including work accounts in the feature rollout does not mean that every public-sharing method has the same conditions for every account type using the product.

Google also specifies what happens when access is withdrawn: deleting the site or turning sharing off invalidates links distributed previously. The resource's identity and access settings remain part of using the material. A separately transmitted file and a link to a resource managed within the product are distinct ways for the information to circulate between people.

Downloading the site file is one of the documented options, alongside opening it in a separate tab, sharing and deletion. Google applies usage limits to generation. The release announcement and help page describe behavior within the product; the export option needs to be read separately from notebook access rights and users' private inputs in the generated site.

Personal and Workspace accounts have different data rules

According to Google's privacy explanations, notebook content is not used directly to train foundation models unless the user chooses to submit feedback. For personal accounts, such feedback can include relevant interaction context, such as prompts, uploaded sources, responses and the associated conversation. The choice to provide feedback is therefore part of the documented data-handling conditions.

Google states that feedback can undergo human review and that some feedback data, disconnected from the account, can be retained for up to three years. Submission through positive or negative ratings can collect context even when history is off. Turning history off and choosing to submit feedback therefore describe different controls within the service's documented behavior.

For Google Workspace and Education, the documentation says uploads, prompts and responses are not used to train models or reviewed by human evaluators, including with feedback. Applicable conditions depend on the account type and the organization's service. Use of other Google services remains subject to the notices and terms governing those particular services and their data.

These differences matter for businesses working with internal documents or materials received from partners. The account used to access the product and the feedback option influence the rules described by the provider. An interface generated from a business's own sources does not make the service an application installed and executed exclusively within that business's own network.

Generated interfaces and operational applications have distinct roles

Google illustrates the feature through tools that make information easier to explore. An operational application additionally has rules concerning shared data, user identity and permitted changes in systems. In this case, private inputs for each person and notebook-linked access are documented behaviors that define how the generated interfaces can be used by the people accessing them.

The connection with custom AI applications arises when a business needs explored information connected to its own process. Source access, shared storage and modification rights require descriptions at the application level. A dashboard's visual example and its integration into a real operational workflow are separate requirements, even when they concern the same business information.

The November 16 release adds a new interactive way of presenting sources within Gemini Notebook. Confirmed conditions are the web rollout for adults, inclusion of Workspace, required notebook permissions and rules for individual inputs. The mobile app is the stage announced for later, while sharing and data processing follow conditions specific to the type of account used.