An interactive view can make a source collection easier to explore, but the link still carries access rules.
Gemini Notebook can now turn source material into interactive sites. Google’s November 18 Workspace announcement describes dashboards, visual explainers, and project trackers generated from a notebook. A user starts by asking the notebook chat to make a site and describing what it should do.
The feature has a broad announced audience: personal Google accounts, Workspace customers, and Workspace Individual subscribers aged 18 or over. It is available on the web, with mobile support described as coming later. The rollout began on November 16 and may take up to 15 days to become visible.
For a founder, the interesting opportunity is to make an existing research or planning collection easier to use. The key constraint is that a generated site stays connected to the notebook’s permissions and product rules. The sharing model deserves attention before a link leaves the team.
Start with a question the sources can answer
A useful site has a defined job. A collection of customer interviews could support an explainer about recurring requests. A set of approved product documents could support a feature comparison. A small sales report could support a dashboard whose totals are easy to verify.
Write that job in the generation request. Name the source collection, the questions a reader should be able to explore, and the calculations that need to remain visible. “Make a dashboard” leaves much more room for an attractive result that answers the wrong question.
For example, use a small synthetic dataset with 100 units in one period and 125 in the next. A dashboard should show a rise of 25 units and a 25% increase from the first period. That arithmetic is an illustrative acceptance check, not a result from a generated Gemini Notebook site.
Keeping the example small helps expose a wrong denominator or label. Once those basics are clear, the same review can extend to the real source material. The product’s ability to generate an interactive display does not establish the accuracy of every number it includes.
Creation, viewing, and public sharing are different permissions
Google’s site-generation help page explains the roles involved. A person needs edit access to generate or delete a site. Viewers need access to the full notebook. Public sharing and access management have additional consumer-account and owner/editor requirements.
| Action | Documented requirement or behavior | Why it matters |
|---|---|---|
| Generate or delete a site | Edit access to the notebook | A viewer’s link does not grant creation rights. |
| View a shared site | Access to the full notebook | Review the source collection before inviting someone. |
| Share publicly and manage access | A consumer account and notebook owner or editor status | Managed-account availability does not establish the same public-sharing rights. |
| Enter information in a shared site | Each user sees only their own site inputs | A tracker’s form fields do not automatically become a shared team record. |
That last row changes how a project tracker is interpreted. A person may check a box or enter a note and see that state when returning. The help page says other users, including the owner, do not see that person’s site inputs.
A team that needs one shared task board should therefore verify how its intended record is stored and shared. Do not treat a familiar-looking checkbox or form as proof of collaborative storage. The documented per-user behavior is useful for personal exploration, while a shared operating record needs its own demonstrated workflow.
Review the notebook before reviewing the site link
Because viewers need notebook access, begin the sharing review with the source list. A founder may have combined public documentation with internal interview notes or a private planning document. A site intended for customers needs an audience-appropriate collection of sources.
A separate notebook containing approved material can make that boundary easier to understand. The owner can check the permitted sources and the intended recipients together. This is a proposed publishing workflow, not a claim that the product automatically separates sensitive material for you.
Review the generated site from the recipient’s account when running an authorized test. A successful owner preview establishes that the owner can view it. It does not establish what a customer, contractor, or signed-out visitor can open.
Google also documents that deleting a site or turning off its sharing breaks previously generated share links. Keep a record of where the link is distributed, particularly if it appears in onboarding material or a newsletter. A later access change may affect those readers.
Keep a visual explanation and an operational tool to different standards
An explainer can be useful when its charts, labels, and interactions help a reader understand the sources. Review the claims and whether a reader can trace an important value back to the notebook material.
An operational tool has additional responsibilities. A task tracker may need shared updates, an audit trail, and a clear way to recover information. A sales dashboard may need a defined refresh process and a reliable source version. Specify those requirements before deciding that a generated interface satisfies them.
The distinction also helps choose a suitable first use. A read-only explainer built from approved public material is easier to evaluate than a tool that appears to commit business changes. Start with the consequence the interaction is supposed to have, then verify that consequence outside the visual presentation.
Our earlier Gemini Notebook overview covers connected-app actions and source management. The new site feature adds another way to present it. Creation of an interactive view and permission to change the underlying notebook remain separate parts of the workflow.
Plan around the rollout and usage limits
Google’s announcement provides a rollout window rather than promising that every eligible account will see the feature immediately. It also says the feature has no separate administrator control, while administrators retain control over who can use Gemini Notebook itself.
For a managed account, confirm that the underlying service is enabled. Then check whether the site-generation option has reached that account. A feature arriving during a staged rollout can appear at different times for colleagues in the same organization.
The help page also states that usage limits apply to creating sites. Include those limits in a team’s workflow planning. A recurring report that depends on frequent regeneration needs a different budget and schedule from an occasional explainer.
A good first deliverable is small enough to verify: approved sources, a defined reader question, a handful of inspectable calculations, and a sharing rule that matches the audience. The interactive result then earns its place by making those sources more useful to the people who can legitimately access them.



