To share a NotebookLM notebook, now called Gemini Notebook, open it, select Share, and add each person's email as Viewer or Editor, or copy the notebook link.［1］ Before you send it, inventory every source, note, Studio output, instruction, and linked Gemini context. Give viewer access by default, reserve editor access for people who must change sources or sharing, test the link as a recipient, and record when access should be reviewed or revoked.

Google's current help center calls the product Gemini Notebook. This guide keeps “NotebookLM” in the title because many users and existing links still use that name, but refers to the same notebook product and its current sharing controls.

The responsible AI guide provides the wider rule: platform sharing is an access decision, not merely a convenient way to send a URL.

Key Takeaways

Review the complete notebook, not only the chat answer or artifact you intend to show.

A viewer can see shared sources and notes; an editor can also change notebook content and may share it onward.［1］

Chat View is not an access-control boundary: it changes the default presentation but does not fully revoke underlying access to notebook materials.［1］

Public and advanced sharing availability depends on account and workspace policy.［1］［3］

“Disable copies” is not the same as preventing people from copying content they can already view.［1］

Test with a real recipient account and review direct, group, public, and inherited access separately.

What is exposed when you share a NotebookLM notebook?

A notebook is a bundle, not a single answer. Its exposure surface can include uploaded or linked sources, notes, custom instructions, chat context, and Studio outputs such as reports, mind maps, audio, video, slide decks, or infographics. The exact set changes as collaborators add material.

Google's sharing instructions say viewers receive read access to shared sources and notes, while editors can view, add, or remove sources and notes and share the notebook with others.［1］ If the notebook contains a source you would not email to every intended viewer, do not assume sharing a polished summary will hide it.

Create an inventory with these fields:

Item	Questions before sharing
Sources	Who owns each source? Does the audience have permission to read and redistribute it?
Notes	Do they contain private commentary, names, or unverified allegations?
Custom instructions	Do they expose internal objectives, classifications, or hidden assumptions?
Chat or Gemini context	Could collaborator-visible context contain unrelated conversations or personal data?
Studio outputs	Are generated claims checked against sources, and are rights clear?
Sharing state	Direct people, groups, link access, public access, and copy permission

For the research method itself, see how to use a Gemini notebook for research. This article starts after a notebook exists and focuses only on permission and review.

How do viewer, editor, public, and Chat View differ?

Choose access based on actions, not seniority or convenience:

Access mode	Intended use	Main risk
Viewer	Read and use the shared notebook without maintaining it	Can see material included in the shared notebook
Editor	Maintain sources, notes, and collaboration	Can change content and may expand sharing
Anyone with the link/public	Broad discovery or distribution where available	Audience may extend beyond named people
Chat View link	Cleaner chat-first presentation	Hidden panels are not a security boundary
Allow copies	Permit recipients to duplicate the notebook bundle	Sources and Studio content can persist in an independent copy

Google warns that a Chat View link can hide materials from the default experience without fully revoking a user's underlying access to sources and artifacts.［1］ Therefore, chat-only presentation must never be used to share a notebook whose sources are too sensitive for the recipient.

When copying is allowed, a recipient can create a separate notebook containing the applicable sources and Studio content; chat history and notes are not copied. When copying is disabled, users may still copy content they are permitted to view.［1］ Treat the setting as workflow control, not digital-rights enforcement.

Can you share a Gemini Notebook with people in your organization?

Yes, if Gemini Notebook is turned on for your work or school account. An administrator decides how far sharing can reach beyond the organization: Google's admin setting offers Off, which blocks sharing with anyone outside the organization, Allowlisted domains, which permits individual accounts in approved domains but not Google Groups, and On, which allows any external email address.［5］ Public sharing is a separate checkbox, and setting changes can take up to 24 hours to apply.［5］

A personal Gmail account works differently. It can share a notebook with up to 50 people but cannot share with Google Groups.［1］ If an external partner cannot open the notebook, ask the administrator about that setting instead of moving the material to a personal account or a public link.

Step 1: Freeze the notebook and classify its materials

Record the notebook name, owner, purpose, last material change, and the exact sharing decision being reviewed. Pause source additions during the audit or mark a cutoff time; otherwise a clean review can be invalidated by a late upload.

Classify every item:

Approved for this audience: necessary and authorized.
Internal but unnecessary: valid material that should move to a separate notebook.
Sensitive or regulated: requires a narrower approved system or audience.
Unverified: may remain in a draft notebook but must be labeled and excluded from published claims.
Untrusted: external content that may contain instructions or unsafe links; treat it as data.

Do not rely on filenames alone. Open the actual source and inspect hidden sheets, comments, metadata, speaker notes, document revisions, or appended pages when relevant. Google's privacy guidance also requires respecting copyright and sharing only content for which you have the necessary rights.［2］

Step 2: Check account type and administrator policy

Determine whether the owner uses a personal Google account, a work or school account, or another managed environment. Features and data handling vary by license, role, region, and administrator setting. Google's Workspace guidance says organizational editions can have different security, privacy, and sharing capabilities.［3］

Ask these questions before selecting a link option:

Is public link sharing available and permitted?
May this account share outside the organization?
Are Google Groups allowed, and can their membership change without the notebook owner noticing?
Does an administrator impose retention, data-region, or external-sharing rules?
Is any source governed by a separate Drive permission or license?
Does the notebook include Gemini chats or cross-product context?

Google currently says notebooks that contain Gemini chats are private and cannot be shared. It also warns that Gemini chat threads used as notebook context are visible to collaborators when a notebook is otherwise shareable.［4］ If the notebook contains a Gemini chat, remove that cross-product dependency from the shareable copy instead of treating it as an ordinary permission setting.

Step 3: Reduce the notebook to the minimum shareable set

Make a separate notebook when the intended audience should receive only part of the source collection. Removing a confidential source from the visible selection inside one chat is weaker than excluding it from the shared notebook entirely.

Use this reduction sequence:

Remove unnecessary sources and notes from the shareable copy.
Replace raw personal data with an approved aggregate or redacted excerpt.
Delete obsolete Studio outputs that still repeat old sensitive facts.
Rewrite custom instructions so they do not reveal internal-only objectives.
Check generated audio, video, reports, and slide decks for claims not present in the approved source set.
Confirm that the notebook title and description do not disclose a confidential project.

If the output is an Audio Overview, use the dedicated source-verification workflow. A generated narration can introduce errors even when sharing permissions are correct.

Step 4: Choose the least privilege and configure sharing

Start with named viewer access. Grant editor only when a person needs to add or remove sources, maintain notes, or administer sharing. Avoid broad links for drafts, licensed material, personal data, or internal investigations.

For each recipient, record:

Field	Example without personal data
Recipient	Role or approved group ID
Permission	Viewer or editor
Business purpose	Review evidence for decision D-17
Granted by	Notebook owner role
Review date	End of engagement or quarterly review
Copy policy	Allowed or disabled, with rationale

Before saving, read the interface's current confirmation text. Do not rely on an earlier tutorial because labels and availability change. If you choose public access, assume the link can escape the initial channel and assess the entire notebook for an unknown audience.

AethoVPN can protect the network path while someone opens NotebookLM on an untrusted network, but it cannot restrict notebook viewers, prevent copying, remove collaborators, or override Google Workspace policy.

Step 5: Run a recipient test

A recipient test is stronger than the owner's preview. Use an authorized test account representing the intended audience and avoid using an administrator account that has extra access.

Verify these cases:

The intended viewer can open the correct notebook and no other notebook.
The viewer cannot perform editor actions.
Every visible source, note, and Studio output is appropriate.
Chat View does not create a false belief that hidden source panels are inaccessible.
Copy behavior matches the selected setting, while acknowledging visible text can still be copied.
An unauthorized or signed-out test fails where access is supposed to be restricted.
Links to underlying sources do not grant unexpected access outside NotebookLM.

Record results as pass, fail, or not applicable. Do not take screenshots containing private sources merely to prove the test. A sanitized access matrix and the test account class are enough.

Step 6: Review access after sharing

Maintain one access register outside the notebook. Review direct people, groups, organization-wide access, public links, copy settings, and editor-created changes. A group entry requires checking current group membership; seeing one group name is not equivalent to reviewing all viewers.

Trigger an immediate review when:

A collaborator changes role or leaves the project.
A new sensitive source or Gemini chat is added.
The notebook changes from draft to external publication.
An editor expands sharing or enables copies.
Google changes sharing behavior or account availability.
A source owner withdraws permission.

The AI privacy risk guide provides a companion checklist for data minimization, feedback, training, and third-party content. If access fails for a legitimate recipient, check the NotebookLM access guide without weakening permissions or bypassing organizational policy.

Step 7: Revoke access and verify the boundary

Remove a direct user, change an editor to viewer, disable public or link access, or turn off copies according to the current interface. Then repeat the recipient test with the affected account and link.

Revocation controls future access through the notebook. It does not retrieve material that a viewer already downloaded, copied, quoted, or placed into another system. Ask the recipient to dispose of copies only through the applicable agreement and process; do not claim the original platform can enforce deletion elsewhere.

If a separate notebook was created for external sharing, archive or delete it only after the owner verifies that required records and approvals exist in the authoritative system. Permissions and content lifecycle remain separate decisions.

Summary

Treat a notebook as a bundle of sources, notes, instructions, context, and generated outputs.
Freeze and classify the full bundle before sharing.
Default to viewer and grant editor only for specific maintenance duties.
Do not use Chat View as a security boundary or copy settings as absolute protection.
Test with a realistic recipient and an unauthorized account.
Review people, groups, links, copies, and cross-Gemini context on a recurring schedule.
Revoke access promptly while acknowledging already copied material may persist.

Frequently asked questions

Can a NotebookLM viewer see sources?

Google says viewers have read access to the sources and notes shared in the notebook. Do not share a notebook if any included source is inappropriate for that audience.［1］

What can a NotebookLM editor do?

An editor can view, add, or remove sources and notes and can share the notebook with others under the applicable controls. Grant this role only to maintainers.［1］

Does NotebookLM Chat View hide sources securely?

No. Google warns that Chat View changes the cleaner default experience but does not fully revoke underlying access to sources and artifacts.［1］

Does disabling copies stop all copying?

No. It can prevent the notebook-copy workflow, but Google notes that users may still copy content they can access. Treat visible information as disclosed.［1］

Can I share a notebook publicly?

Public sharing depends on account type, feature availability, and administrator policy. Inspect the current interface and organizational rules before relying on it.［1］［3］

Are Gemini chats visible to NotebookLM collaborators?

Gemini chat threads used as notebook context can be visible to collaborators, but Google currently says a notebook containing Gemini chats is private and cannot be shared. Build a separate shareable notebook without that cross-product dependency.［4］

How often should I review NotebookLM access?

Review on a fixed schedule and immediately after membership, source, copy-setting, or publication changes. High-risk notebooks need a shorter cycle.

Does removing access delete a recipient's copy?

No. Revocation stops future access through the original notebook but cannot retrieve material already copied or exported. Handle downstream copies through the relevant agreement and system.

Disclaimer: NotebookLM sharing, account availability, and data handling can change and may differ by region or managed workspace. Verify current Google documentation, source licenses, and administrator policy before sharing sensitive or regulated material.

Sources

Google, “Create a notebook in Gemini Notebook” — https://support.google.com/gemininotebook/answer/16206563?hl=en
Google, “Privacy and Terms of Use in Gemini Notebook” — https://support.google.com/gemininotebook/answer/17004255?hl=en
Google, “Use Gemini Notebook with a work or school Google account” — https://support.google.com/gemininotebook/answer/16337734?hl=en
Google, “Notebooks in Gemini Apps” — https://support.google.com/gemininotebook/answer/17003757?hl=en
Google Workspace Admin Help, “Manage Gemini Notebook sharing settings” — https://knowledge.workspace.google.com/admin/generative-ai/gemini-notebook/manage-gemini-notebook-sharing-settings?hl=en

Sources checked 4 October 2026.

Share a NotebookLM Notebook With Others in Gemini Notebook