Gemini Notebook (Formerly NotebookLM) for Small Business Teams

Put one subject's documents (the staff handbook, customer policies, price lists or supplier terms) into a shared notebook at notebook.google.com, and staff can ask questions that are answered only from those sources, with citations. Small teams use it for onboarding, policy lookups and preparing customer answers. It's included with Google Workspace, and personal accounts get a free tier.

The value is the grounding. A general chatbot answers "what's our refund policy?" by guessing what a typical business would do; a notebook answers from your policy and shows the passage it used. That makes it trustworthy in a way plain chat isn't, but only as trustworthy as the sources. Google Docs, Sheets and Slides added from Drive now update automatically; uploaded PDFs, web pages and copied text don't, and stale sources are the main way notebooks go wrong.

Follow me on Instagram@sagnikteaches

How a notebook differs from asking Gemini directly

Gemini Notebook, which Google renamed from NotebookLM in July 2026, sits between two other tools you may already use. The difference is where the answers come from.

Connect on LinkedInSagnik Bhattacharya

A useful way to choose: if the job is "write this the way we always do", build a Gem. If the job is "find out what our documents say about this", build a notebook. Many businesses end up with both, and a Gem (becoming a skill from November 2026) can even use a notebook as one of its knowledge sources.

Subscribe on YouTube@codingliquids

Plan limits that shape how you organise notebooks

Google's Gemini Notebook upgrade page sets out the tiers. For personal accounts, as of September 2026:

Workspace accounts get limits mapped from their edition, so check what your plan allows in the product itself. Two more limits matter in practice. Each source can be up to 500,000 words or 200MB for an uploaded file, so a whole handbook fits comfortably as one source. And since 2 September 2026, usage counts against a quota that depends on how complex each request is, so a team hammering one notebook with long questions may hit limits sooner than a simple message count suggests.

For a small team, 50 sources is usually enough per notebook, which is a hint about organisation: one notebook per subject, not one notebook for the whole business. Sharing doesn't pool limits either; each person keeps the limits of their own plan.

Setting up a team notebook in an afternoon

1. Choose the subject. Pick the area people ask each other about most. For many small businesses that's the staff handbook and policies.
2. Gather the current versions. One version of each document. Delete or archive the rest now, not later.
3. Create the notebook. At notebook.google.com, select Create new notebook and give it a plain name: "Staff handbook and policies".
4. Add sources, preferring Drive. Select + Add. Google Docs, Sheets and Slides from Drive sync automatically every few minutes; Word, PDF, text, Markdown, CSV and PowerPoint files are accepted as uploads but won't update. Where you can, keep living documents as Google Docs.
5. Ask it five test questions you already know the answers to, and click each citation to see it points to the right passage.
6. Share it. Select Share, add colleagues' email addresses, and choose Viewer (read-only access to sources and notes) or Editor (can add and remove sources and notes and share further). Most staff should be viewers.
7. Write a one-line pinned note saying who owns the notebook and when sources were last checked.

Some things to know while sharing: personal Gmail accounts can share a notebook with up to 50 people, but not with Google Groups. On paid tiers, you can share in a chat-only view that hides the source panel for a cleaner experience, though Google notes it doesn't remove the viewer's underlying access to the contents.

Five jobs a small team can hand to a notebook

The examples below come from an illustrative music school: four part-time teachers, an owner who also teaches, and an administrator, around 120 pupils, lessons at the school and in pupils' homes.

1. Getting a new teacher up to speed

The school's handbook notebook holds the staff handbook, the safeguarding procedure, the lesson-cancellation policy, the room booking rules and a Google Sheet of term dates. A new teacher asks:

What do I do if a pupil's parent hasn't arrived 15 minutes after a lesson ends?

An illustrative answer: wait with the pupil inside the building, call the parent and then the second contact on the pupil's record, inform the owner, and never drive a pupil home, citing section 4.2 of the safeguarding procedure. What you'd check: that the citation opens the current procedure, not a draft. The first time the school tried this, the answer quoted an old version that said "wait 10 minutes", because both versions were in the notebook.

2. Policy lookups during a busy day

The administrator gets a call: a parent wants a refund for three lessons missed through illness. Instead of hunting through a PDF, they ask the notebook what the policy says about lessons missed for illness and whether notice periods apply. The answer, with a citation, takes seconds. The decision on any goodwill gesture stays with the owner, but everyone quotes the same policy.

3. Preparing answers for parents

A second notebook, "Parent information", holds the fees sheet, the term calendar, exam board syllabus summaries the school wrote itself, and the FAQs page from the website. Before a parents' evening, the owner asks it to list the questions parents most often raise that the documents answer badly. An illustrative output notices that the fees sheet doesn't say whether exam entry fees are included. That's a gap in the documents, found before a parent points it out.

4. Comparing contracts and terms

When the school considered moving its summer concert, the owner put three venue hire agreements into a temporary notebook and asked:

Compare cancellation terms, deposit, insurance requirements and piano hire across
the three venue agreements. Put it in a table and cite each figure.

The table took a minute. Checking every cited figure took ten, and one was wrong: a deposit quoted from a sample schedule at the back of one agreement rather than the actual terms. The notebook sped up the comparison; the owner still read the clauses that mattered before signing. Temporary notebooks like this should be deleted once the decision is made.

5. An Audio Overview for staff who don't read long emails

When the school updated its safeguarding procedure, the owner generated an Audio Overview, a podcast-style conversation between two AI voices about the changes, and shared it with the teachers, who mostly listen while travelling between pupils' homes. It doesn't replace reading the procedure, but more teachers knew what had changed at the next staff meeting. Check the audio before sharing: AI-generated voices can stress the wrong point or skip a detail.

Notebooks that suit other small businesses

The same pattern (one subject, current sources, questions staff already ask) fits most small teams. Three sketches:

• A dry cleaner's equipment and chemicals notebook. Sources: the manuals for the pressing and cleaning machines, the supplier's safety data sheets, and the shop's own treatment guide. A new assistant asks "what's the cool-down procedure before cleaning the press head?" and gets the manual's steps with a page citation. The rule for this one: anything about chemical handling is checked against the safety data sheet itself, not just the answer, because a paraphrased safety instruction is the wrong place to save thirty seconds.
• A garden centre's plant knowledge notebook. Sources: growers' availability lists and care sheets, the centre's own planting guides, and a Sheet of which plants are toxic to pets. Weekend staff ask "is this shrub safe for a garden with a dog?" and get an answer grounded in the Sheet. The owner's rule: if a plant isn't in the Sheet, staff say "we'll check and call you back" rather than trusting a general answer.
• A picture framer's materials and pricing notebook. Sources: supplier moulding catalogues, glazing specifications, the conservation framing notes the owner wrote, and the price matrix as a Google Sheet. The part-time framer asks which glazing blocks the most UV for a watercolour and which mouldings come in the 40mm profile, and gets cited answers. Because the price matrix is a synced Sheet, a price change the owner makes on Monday is in the notebook's answers the same day.

Across all three, the notebook replaces a question to the owner, not the owner's judgement. That's the right expectation to set with staff on day one.

A music school's first term with notebooks

Week 1 (about three hours). The owner gathered documents, found two versions of the cancellation policy and three of the handbook, and deleted the old ones. Two notebooks went live: "Staff handbook and policies" (14 sources) and "Parent information" (9 sources). Teachers got viewer access; the administrator got editor access to the parent notebook.

Weeks 2 to 4. Questions to the owner by text and phone, which the owner had been fielding at about 15 a week, dropped to around 6. The questions that still came through were about decisions, such as swapping a room or covering a lesson, not about what a policy said.

Week 5. A problem surfaced: the term dates Sheet had been replaced with a new file for next term instead of updated, so the notebook kept answering with old dates. The fix was to put next term's dates into the same Sheet that was already a source, so the sync carried them through. From then on, the rule was "edit the source file; never replace it".

Weeks 6 to 12. A new teacher joined and used the handbook notebook for their first fortnight; the owner estimated it saved around two hours of shadowing and questions. Total ongoing cost: nothing beyond the school's existing Workspace plan, plus about 20 minutes a month checking sources. These numbers are illustrative; count your own "quick questions" for a fortnight before and after.

Keeping answers current

Most notebook failures are source failures. A routine that prevents them:

• Prefer living Google files. Docs, Sheets and Slides from Drive sync; everything else is a snapshot. If a PDF is the official copy, keep a Google Doc version as the notebook source and regenerate the PDF from it.
• Edit, don't replace. Replacing a file with a new one breaks the link to the notebook, as the term-dates example showed.
• One version per document. Contradictory sources produce contradictory answers, sometimes both in the same reply.
• Watch what doesn't import. Google says footnotes and comments in Drive files aren't imported. A policy that relies on a footnote for an exception loses it.
• Check permissions when people change roles. Google says that if someone loses access to a Drive file, it becomes inaccessible as a source, and deleted Drive files are removed from notebooks automatically.
• Monthly five-question test. Ask the same five questions each month and confirm the answers still match current policy.

Sharing and privacy settings to check first

• Viewers see everything. A viewer has read-only access to all the sources. Never put salaries, disciplinary notes or pupils' personal details into a notebook shared with the whole team. Those belong in separate, restricted files.
• External sharing is off by default on Workspace. Since September 2026, admins can choose Off, Trusted domains, On, or On with public notebook sharing, by domain, organisational unit or group. Leave it off unless there's a clear need.
• Personal accounts are different. A teacher using a personal Google account for a work notebook puts school documents under consumer terms and outside the school's control. Use work accounts for work notebooks.
• Usage analytics need an audience. Notebook analytics appear only when a notebook is shared with at least four other people and has had chat activity in the past week, so tiny teams may not see them.

For the underlying question of what data belongs in any AI tool, see organising shared files so AI tools can use them, which covers folder structure and permissions before you point a notebook at them.

Where notebooks mislead, and how you'd notice

• A confident answer from the wrong passage. The venue deposit example: the citation looked right until you opened it. For money, dates and legal terms, always click through.
• Questions the sources don't cover. A notebook is designed to answer from its sources, but a loosely worded question can pull in a loosely related passage. If the answer seems to stretch the source, ask "quote the exact sentence that says this".
• Poor audio or messy imports. Google notes that low-quality audio files can fail to import, and web imports capture only a page's text. Check a source's preview after adding it.
• Stale snapshots. An uploaded PDF from last year answers as if it were current. Put a date in every uploaded file's name so the age is visible in the source list.

If you need something bigger, such as a knowledge base customers or several tools can query, compare the options in AI knowledge base options for small businesses and the groundwork in building a company knowledge base AI can answer from. For onboarding specifically, a notebook works well alongside a structured first-fortnight plan for new starters.

Gemini Notebook for teams: follow-up questions

Is Gemini Notebook a different product from NotebookLM?

No. Google renamed NotebookLM to Gemini Notebook in July 2026. Existing notebooks, sources and shared links carried over automatically, so nothing needs moving. Notebooks also sync with the Gemini app, where you can open and create them directly, but the standalone Gemini Notebook site remains the fullest way to manage sources and sharing.

Can customers use our notebook to get answers?

You can share a notebook with external people if your Workspace admin allows it, and paid tiers offer a chat-only view. But a notebook isn't a customer service tool: there's no handover to staff, no branding and viewers can still reach the source documents. Keep notebooks for staff, and use a proper support tool for customers.

Does Google use our notebook documents to train its models?

On Google Workspace business accounts, Google says Gemini features, including Gemini Notebook, don't use your content to train its models. Personal accounts run under consumer terms, so check the privacy settings there before uploading business documents. Either way, avoid adding anything you wouldn't want every notebook viewer to read.

How many notebooks should a small team have?

Fewer than you'd think. One notebook per subject that people genuinely ask questions about, such as the staff handbook, customer policies or supplier contracts, usually means three to six for a small business. Mixing unrelated topics in one notebook makes answers worse, while dozens of tiny notebooks means nobody can find the right one.

Further reads

• What Gemini in Google Workspace Includes on Each Business Plan — What your Workspace edition includes, Gemini Notebook among it.
• Is Gemini Safe for Confidential Business Data in Workspace? — Privacy questions to answer before uploading policies and contracts.
• How to Set Up Claude Projects as a Shared Team Assistant — The Claude alternative for a shared, document-grounded assistant.
• Custom GPT vs Claude Project vs Gemini Gem: Which Should You Use? — How Gems, Projects and custom GPTs compare for team use.
• How to Write SOPs With AI: From Rough Notes to Clear Procedures — Turn know-how in people's heads into sources a notebook can use.
• How to Onboard New Hires Onto Your AI Tools and Rules — Teach new starters the AI tools and rules alongside the notebook.
• How to Summarise Bundles and Transcripts With AI Safely — Clear the tool, prepare the bundle so page references survive, ask for referenced summaries, then check references, omissions and adverse documents.
• Reusing Past Client Work With AI Without Leaking Client Data — How consultants and small firms turn old client reports into a reusable AI library: contract checks, three reuse tiers, sanitising, and access controls.
• How to Do Competitor Research With AI in One Afternoon — A timed four-hour plan for profiling three to five rivals with AI, from a checked source pack to a one-page grid and two or three decisions.
• How to Use Gemini in Google Docs to Draft and Edit Faster — Drafting from @-mentioned files, Refine before and after, Help me create with a template, and the number mistakes to catch before you accept.
• What Is RAG? A Plain-English Explainer for Business Owners — RAG explained without jargon: how AI looks up your own documents before it answers, traced through a real-looking policy question.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Google Workspace Updates, NotebookLM is now Gemini Notebook (July 2026), Keep your sources up to date with automatic Drive syncing (May 2026) and Manage external sharing for Gemini Notebook in the Admin console (September 2026); Gemini Notebook Help, Upgrade Gemini Notebook, Create a notebook, and Add or discover new sources; Google product announcement on the rename (July 2026).