NotebookLM, now called Gemini Notebook, lets any user turn a stack of internal documents into a shareable, queryable AI notebook, and the copy of those documents it keeps sits outside the Drive sharing and data region settings your organisation already relies on. Google announced the rename on 16 July 2026; the product, its web address and existing shared notebooks carried on working through automatic redirects, so most staff still search for it as NotebookLM. This guide covers the customer-side controls Google documents for managed Workspace accounts: who can use the service, what data protection terms apply by edition, how notebook sharing works, what the audit log records, and how to keep sensitive files out. It is written for Workspace administrators, security architects and data protection teams deciding whether, and how, to allow it for work documents. Broader Gemini controls (Gemini in Gmail, Docs and the Gemini app) are covered in the Gemini for Google Workspace Security Guide; this page goes deeper on the notebook product only.
This is an independent guide from NHI Mgmt Group, based on Google's public documentation as of November 2026. It is not sponsored or reviewed by Google. Product features change, so confirm settings against Google's current documentation.
Key takeaways
- One service setting decides access. Admin console > Generative AI > Gemini Notebook > Service status turns the product on or off by organisation, organisational unit (OU) or access group, and it also governs whether users can add notebooks as a source in the Gemini app.
- Your edition sets the data terms. Core service editions get enterprise-grade protections (no human review, no model training on uploads, chats or outputs); editions where it is an additional service run under the Google Terms of Service, where feedback can be reviewed.
- Sources are copied, not referenced. A Drive file added as a source becomes a copy stored with the user's notebook data, and Google states that file sharing and data region settings do not apply to that copy.
- External sharing is now a separate control. Since September 2026 the Gemini Notebook sharing setting offers Off (the announced default), allowlisted domains, On, and On with public sharing, applied per OU or group.
- The audit log closes the visibility gap. The gemini_notebook activity log records notebook, source and studio events with a visibility value, so you can alert on notebooks shared externally or made public and on sources pulled from local uploads.
What Gemini Notebook is and where the risk sits
A notebook is a container of sources (Drive files, local uploads, pasted text and web URLs) plus a chat grounded in those sources and "studio" outputs such as Audio Overviews, Video Overviews, reports, flashcards, quizzes, slides and infographics. Users can share a notebook with colleagues, and in January 2026 Google added the option to attach a notebook as a source inside the Gemini app, which means notebook content can also feed Gems, Canvas and Deep Research.
The security questions are therefore less about the model and more about data movement:
- Copy on upload: the Privacy Hub states that when a user uploads a source from Drive, a new copy is stored with the user's notebook data rather than in Drive. Revoking someone's access to the original Drive file does not pull the copy out of a notebook that was already shared with them.
- Region and residency: Google states that organisation data region settings do not apply to data processed and cached by Gemini Notebook, and the September 2026 audit log announcement says notebooks, sources and chat histories are stored globally. Teams bound by data residency commitments need to decide which OUs may use it.
- Re-sharing: a user with view access to a sensitive Drive file can summarise it into a notebook and share that notebook. The Drive permission check happens when the source is added; Drive sources can be used only by people with at least view access to the original file.
- Untrusted sources: web URLs and pasted text are untrusted content that the model reads as instructions as well as data. Treat notebooks built on external pages with the same caution as any retrieval system exposed to OWASP LLM01:2025 Prompt Injection.
Editions, terms and data protection
Google's admin page for the service groups editions into access tiers. The data protection terms follow the tier, so the first job is to confirm which row your users sit in.
| Edition group (as listed by Google, November 2026) | Service type | Terms and data handling |
|---|---|---|
| Business Base, Essentials Starter, Workspace Individual, G Suite, Cloud Identity, Chrome Enterprise, Android Enterprise | Standard access, additional service | Google Terms of Service. Data is not used for training unless the user gives feedback; feedback review may include the full interaction. Data may be processed to prevent fraud, abuse and technical issues. |
| Business Starter, Enterprise Starter, Enterprise Essentials and Essentials Plus, Frontline Starter, Standard and Plus, Nonprofits, Education Fundamentals and Standard | Standard access, core service | Google Cloud Terms (Workspace for Education Terms for education). Uploads, chats and outputs are not reviewed by human reviewers or used to improve generative AI models; covered by the Cloud Data Processing Addendum. |
| Education Plus, Teaching and Learning add-on | More access, core service | As core service. |
| Business Standard and Plus, Enterprise Standard and Plus, Google AI Pro for Education | Higher level access, core service | As core service, with higher usage limits. |
| AI Expanded Access and AI Ultra Access add-ons | Expanded and highest access, add-on | Highest usage limits (for example up to 600 sources per notebook at the top tier). |
Retention: the Privacy Hub states that prompts and responses are not retained after the session ends, while uploaded files and user-created notebooks follow the deletion terms in Section 6 of the Cloud Data Processing Addendum. Users can delete or export them; admins can use the Data Export tool and users can use Takeout.
Assurance scope: Google's pages differ here as of November 2026. The service admin page lists SOC 1, 2 and 3, several ISO/IEC certifications, BSI C5:2020, MTCS, OSPAR and ISMAP, while the Privacy Hub states that Gemini Notebook does not currently carry ISO, SOC or FedRAMP coverage and is outside the Google BAA for HIPAA. Treat the more cautious statement as your working position, record the discrepancy in your risk register, and keep regulated health data out until Google's compliance pages confirm coverage. The January 2026 Gemini app announcement makes the same point from the other side: notebook use inside Gemini is subject to the notebook's certifications, which may differ from Gemini's.
Age-gated features: from 23 September 2026 Google limits Interactive Mode in Audio Overviews, Cinematic Video Overviews, Deep Research, Infographics and Slides to users aged 18 and over; the core notebook, chat and most studio outputs are available to all ages. Education admins should review this against their age-based access settings.
Access control: who can use it
The service setting needs the Gemini Settings administrator privilege. Keep that privilege on a small named group; it controls every Gemini feature, not just notebooks.
- Decide the default: at the top-level OU choose On for everyone or Off for everyone. For education editions Google turned the service on by default as a core service when it reached all ages in August 2025, so check the current state rather than assuming it is off.
- Scope by OU or group: set Service status per OU, using Override to pin a local value when the parent changes and Inherit to return to the parent. Access groups let you enable a pilot cohort across OUs without restructuring the directory.
- Add Context-Aware Access: Google documents Context-Aware Access for the service (announced March 2025 for Enterprise Standard and Plus, Education Standard and Plus, Enterprise Essentials Plus, Frontline Standard and Cloud Identity Premium). Require a managed or compliant device and, where it fits, corporate network ranges for the OUs that handle sensitive material.
- Remember the Gemini app path: turning the notebook service off also removes the ability to add notebooks as a source in the Gemini app, because that feature follows the notebook setting rather than the Gemini app setting.
- Treat personal accounts as shadow AI: the service setting governs managed Workspace accounts. Staff signing in with personal Google accounts are outside it; handle that with your acceptable use policy and discovery tooling. See the Shadow AI Discovery Guide.
Sharing controls
Before September 2026 the only admin lever was the on or off service toggle. Google's 10 September 2026 update added a dedicated Gemini Notebook sharing setting under the same Generative AI page, configurable at domain, OU or group level, with no end-user override.
| Option ("Sharing outside of [organisation]") | What users can do | When to choose it |
|---|---|---|
| Off (announced default) | Share notebooks only inside the organisation. | Most OUs; any team handling personal, financial, legal or health data. |
| Allowlisted domains | Share with individual accounts in listed domains. Sharing with Google Groups in those domains is not supported. | Joint ventures, agencies and auditors with a stable domain. Reuse the trusted domain list you maintain for Drive. |
| On | Share with any external email address. | Rarely; teaching, research or community programmes with no sensitive sources. |
| On with Public Sharing ticked | Make a notebook available to anyone with the link. | Marketing or public education teams publishing deliberately public material, in a separate OU. |
Google notes that changes can take up to 24 hours. Its help page does not describe what happens to notebooks already shared externally when you tighten the setting, so after any change query the audit log for notebooks whose visibility is still shared_externally or public and follow up with their owners.
Inside a notebook, owners decide who can view or edit and, on paid tiers, use advanced sharing options. Internal oversharing is the more common problem than external sharing: a notebook built from a board pack and shared with "everyone at" the company is a fresh copy of the board pack with a chat interface.
Keeping sensitive data out
As of November 2026 the Privacy Hub directs admins to Information Rights Management rather than Workspace DLP to keep Drive files out of notebooks: files with download, copy and print disabled for viewers and commenters cannot be uploaded as sources. A layered approach looks like this:
- IRM on sensitive Drive content: apply "disable download, print and copy" to the shared drives and folders that hold restricted material, ideally driven by classification labels so it scales. See the Information Rights Management vs DLP guide for the trade-offs.
- OU separation: leave the service off, or sharing Off, for OUs whose data cannot leave your residency boundary.
- Local uploads and URLs: IRM only covers Drive. Files uploaded from a laptop and pasted text bypass it, so endpoint and browser controls and the acceptable use policy carry that risk. See the Google Workspace DLP Guide for what Workspace DLP does cover.
- Clear user guidance: tell staff which data classes may go into a notebook, that deleting the original Drive file does not delete the notebook copy, and how to delete notebooks they no longer need.
Logging and detection
Google announced comprehensive audit logs for Gemini Notebook on 3 September 2026. They appear in the security investigation tool and the audit and investigation tool, carry user identity, IP address, resource context and notebook visibility, and can be exported to BigQuery once an admin turns that export on (it is off until enabled). Audit logs follow standard Workspace regional routing even though notebook content is stored globally. Through the Admin SDK Reports API the application name is gemini_notebook and events have type notebook_activity.
| Event | Useful parameters | What to watch for |
|---|---|---|
| create_notebook, copy_notebook | visibility, notebook_copy_id, ai_plan_tier | Copies of notebooks owned by others; bursts of creation by leavers or recently compromised accounts. |
| view_notebook | visibility | Views of notebooks with visibility shared_externally or public, especially from unfamiliar IP addresses. |
| add_source | source_type (drive, local_upload, copied_text, url), source_name, source_url | Drive sources whose names match restricted projects; high volumes of local_upload; URLs pointing to personal file-sharing sites. |
| view_source, delete_source, rename_source | source_id, source_name | Renaming that hides a source's origin; deletion spikes after an investigation starts. |
| chat, discover_sources | visibility, ai_plan_tier | Usage baselines per OU, to size the programme and spot unexpected adoption. |
| delete_notebook, delete_studio_artifact | studio_artifact_id | Mass deletion before departure or during an incident. |
Forward the events to your SIEM alongside Drive and login logs; a pattern of Drive download plus add_source plus external visibility is more telling than any one event. See the Google Workspace Audit Log Detection Guide for collection and rule design.
Metrics that show the controls are working:
- Number of notebooks with visibility shared_externally or public, trended weekly, with each one having a named business owner.
- Share of add_source events of type local_upload versus drive in high-risk OUs.
- Percentage of restricted shared drives with IRM applied.
- Count of OUs where the service is on without Context-Aware Access, target zero for sensitive OUs.
- Time from an alert on a public notebook to owner review.
Rolling it out safely
- Inventory first: confirm the edition of every OU, current Service status and whether education defaults have already switched it on. Pull any existing gemini_notebook events to see real adoption.
- Set the guard rails before the pilot: sharing Off at the root, Context-Aware Access for the pilot group, IRM on restricted shared drives, BigQuery export on.
- Pilot with an access group: one or two teams with ordinary data, two to four weeks. Review add_source types and visibility weekly and collect the questions users ask.
- Publish the rules: update the AI acceptable use policy with the permitted data classes, the copy-on-upload behaviour and the deletion expectation. The AI Acceptable Use Policy Template is a starting point.
- Expand by OU: enable OU by OU, granting allowlisted domains only where a named business need exists.
- Roll back cleanly: setting Service status to Off for an OU removes access (allow up to 24 hours), and turning sharing back to Off stops new external shares. Existing notebooks remain until deleted under the Cloud Data Processing Addendum terms or by their owners, so export or review them as part of any rollback.
Small versus large organisations: a small business on a core service edition can usually run with service On, sharing Off and a one-page usage rule, reviewing external visibility monthly. Large and regulated organisations need OU separation for residency, Context-Aware Access, IRM by label and SIEM alerting before broad enablement.
Where identity fits
Every notebook action is attributed to a user identity, so the controls that protect Workspace accounts protect notebooks too: phishing-resistant sign-in, session length limits and prompt suspension of leavers. Offboarding should include transferring or deleting notebooks that hold company material, because they are stored with the user's notebook data rather than in a shared drive. The Gemini Settings administrator privilege is itself a privileged role and belongs in your access reviews.
Common failure patterns
- Assuming Drive permissions follow the content: removing a colleague from a Drive folder leaves the notebook copy readable by anyone the notebook is shared with.
- Relying on Workspace DLP for notebooks: DLP rules written for Drive and Gmail do not stop sources being added; IRM and OU scoping are the documented route.
- Forgetting the Gemini app link: leaving the notebook service on for an OU where Gemini app use is restricted still lets users attach notebooks to Gemini chats and Gems.
- Granting external sharing domain-wide: turning sharing On at the root for one partner project opens every OU; use an OU or group override with allowlisted domains instead.
- Ignoring the education default: institutions that never touched the setting may already have the service on for all ages.
- Logging without review: BigQuery export left off, or events collected but never queried for public visibility.
Framework mapping
| Control area | NIST SP 800-53 Rev 5 | NIST CSF 2.0 | ISO/IEC 27001:2022 Annex A |
|---|---|---|---|
| Service enablement by OU, group and Context-Aware Access | AC-3 Access Enforcement | PR.AA-05 | A.5.15 Access control |
| External and public notebook sharing | AC-21 Information Sharing | PR.DS-01 | A.5.14 Information transfer |
| Use of an AI service outside existing residency controls | AC-20 Use of External Systems | GV.OC-03 | A.5.23 Information security for use of cloud services |
| Audit events and review | AU-2 Event Logging, AU-6 Audit Record Review, Analysis, and Reporting | DE.CM-03 | A.8.15 Logging, A.8.16 Monitoring activities |
| Notebook retention and deletion | SI-12 Information Management and Retention | PR.DS-01 | A.8.10 Information deletion |
Practitioner checklist
- Confirm every OU's edition and record whether the service runs under core service or Google Terms of Service.
- Restrict the Gemini Settings administrator privilege to a named group and review it quarterly.
- Set Gemini Notebook sharing to Off at the root; use OU or group overrides with allowlisted domains for named needs only.
- Apply Context-Aware Access to OUs that handle sensitive data.
- Apply IRM (disable download, print and copy) to restricted shared drives so their files cannot become sources.
- Turn on BigQuery export for audit logs and alert on shared_externally and public visibility.
- Record the compliance scope discrepancy and keep HIPAA-regulated data out until Google confirms coverage.
- Add notebook transfer or deletion to the leaver process.
- Publish user rules covering data classes, copy-on-upload and deletion.
Standards and references
- Google: Generative AI in Google Workspace Privacy Hub
- Google: Turn Gemini Notebook on or off for users
- Google: Manage Gemini Notebook sharing settings
- Google: Gemini Notebook Audit Activity Events (Admin SDK Reports API)
- Google Workspace Updates: Comprehensive audit logs for Gemini Notebook
- Google Workspace Updates: Manage external sharing for Gemini Notebook
- Google Workspace Updates: NotebookLM is now Gemini Notebook
- OWASP: LLM01:2025 Prompt Injection
Related NHI Mgmt Group resources: Gemini for Google Workspace Security Guide · Google Workspace Security Guide · Shadow AI Discovery Guide · AI Data Retention and Deletion