Latest in AI
Gemini Notebook Sites: Build a Dashboard and Check What You Share
Create an interactive site from notebook sources, check sharing permissions and understand why saved inputs do not make it a shared team tracker.
Gemini Notebook can now turn source material into interactive sites. The useful question is not whether it can produce a dashboard. It is whether the dashboard presents the right evidence, reaches the intended readers and behaves the way those readers expect.
Google's November 16 announcement describes a global web rollout for adults, including Workspace users, with mobile support coming later. This guide is based on documentation, not a hands-on test. The prompts and checks below are proposed starting points.
Start with a small notebook, not your whole workspace
For a first attempt, use a training guide or an internal explainer rather than a customer reporting dashboard. A good starter project has three or four short sources, a clear audience and facts you can verify without opening another ten documents.
Create a separate notebook containing only material that audience may read. Give sources meaningful names, such as “Onboarding schedule” and “Product glossary,” rather than relying on upload filenames. This makes it easier to notice when the output combines the wrong sources or invents a relationship between them.
Google's source documentation explains how to add material and select sources for a request. It also distinguishes source updates from generated outputs: changing or deleting a source does not change Studio outputs already generated from it. Put a review date on your project and plan to recheck the site when the underlying material changes.
Ask for a specific reading experience
In a notebook you can edit, ask Chat to make a site and describe the result. Open the generated artifact from Studio. Google's site instructions also provide an Open in new tab option.
Here is an original prompt to adapt, not a tested recipe:
Make a site from the selected onboarding sources for a new teammate. Organize it by week and topic. Include a glossary, a searchable reading list and a personal checklist. Show which source supports each factual section. Mark missing dates as unknown instead of inventing them. Do not include a submission form or suggest that checklist progress is visible to a manager.
The point of those constraints is to make review easier. Asking for source labels does not guarantee that every label or claim will be correct. Pick a known date, a definition and an exception from the documents, then trace each through the generated page. A polished chart is not evidence that its numbers are right.
Try an empty search and a filter combination with no results. The page should explain that nothing matches, not quietly show unrelated content. If it contains calculations, check one manually before giving the page to anyone else.
Saved inputs are personal, not a shared task database
Google says site inputs persist, but every user, including the owner, sees only their own inputs. That makes a personal reading checklist a better fit than a team completion register.
My practical interpretation is to treat the site as an interactive presentation until you have verified every workflow you need. Do not tell managers that checking a box records employee completion. Likewise, a text field should not be presented as a way to submit customer feedback without a separately verified collection mechanism.
For a pilot, ask two colleagues to enter different harmless values. Have each reopen the site and report what appears. This proposed test checks expectations without putting real customer information into an unreviewed interface.
Review the notebook before sharing the site
The site-specific instructions require viewers to have full notebook access. Public sharing and access management require a consumer account and an owner or editor role. From Studio, use More, then Share, check notebook access, copy the artifact link and save.
That is why the separate notebook matters. Review the source list as carefully as the visible page. Do not assume hiding a detail from the generated layout removes it from the material available to recipients. Downloading a file is also a distribution decision, not a substitute for reviewing its contents.
Budget for revisions
Consult Google's usage-limit guidance and the Settings usage view before planning a deadline around repeated generations. Consumption depends on the work requested; there is no universal number of sites promised by this guide.
Begin with one narrow version, collect corrections together and revise deliberately. Keep a short acceptance note covering factual accuracy, source access and expected interaction behavior. That note will be more useful on the next revision than simply remembering that the first version looked good.
I'm Paras. I work at the intersection of AI, engineering and distribution.
I help teams turn AI-generated prototypes into useful workflows with clear data and review boundaries.