MILabs
Integrations

Staff knowledge assistant for Google Workspace, built on Drive and Docs

How a staff knowledge assistant answers team questions from approved Google Drive and Docs files, with each reply citing its source.

Updated 2026-05-23

Staff knowledge assistant with Google Workspace

A staff knowledge assistant for Google Workspace reads the policies, procedures and reference documents your team already keeps in Drive, Docs and Sheets, then answers staff questions in a browser chat. Because Workspace holds shared folders, file ownership and sharing rules in one place, the assistant can be limited to an approved folder rather than the whole account. A folder shared company-wide may contain drafts nobody has checked, and a team folder may hold material that belongs only to that team. Before anything is connected, you and your team lead decide which folders count as current and which Google account the assistant reads through. The first working step is mapping that set together, so every answer can point back to a named file and section. Google's Drive API lets an outside tool read those files with the owner's permission, which means updates made in Drive can flow through without a manual re-upload.

How it works

  1. Map the folders by listing which Drive folders and Docs or Sheets files hold current policies, then confirm each owner and sharing setting with your Workspace administrator.

  2. Connect a dedicated account to the Drive API with the narrowest scopes that still allow reading approved files, so the assistant cannot edit anything.

  3. Index the approved files by splitting each into sections and storing them in a Pinecone index, with the file name and heading kept beside every section.

  4. Answer through Claude, reached via the Anthropic API, which drafts each reply from the retrieved sections and names the file it relied on.

  5. Refresh the index when a mapped file is edited in Drive, so its sections are indexed again and old wording does not survive.

  6. Review flagged answers by letting staff mark a reply that looks wrong, then having the team lead decide whether the source document needs changing.

good questions, straight answers

Frequently asked questions

Do I need a developer to connect a staff knowledge assistant to Google Workspace?
Some development work is needed, because the assistant reads files through the Drive API and needs a small amount of code to index them and return answers with sources. A business does not have to write that code from scratch, and the Workspace admin still sets which account the tool uses and which folders it can see. Your team's role is mostly content and access decisions: which documents are current, and who should be able to ask questions about them.
How does a staff knowledge assistant stay in step with Google Workspace?
Changes are picked up from the source rather than copied by hand. When a mapped file in Drive is edited, its sections are re-indexed, so a revised procedure replaces the old wording in later answers. Deleted or moved files need a matching update to the mapping list, which is why the team lead reviews the folder set on a regular schedule. Sharing changes made by the administrator also matter, because the assistant only reads what its account can already see.
How do I know a staff knowledge assistant works with Google Workspace?
You check it against your own folders before staff rely on it. Choose questions the team already answers by hand, run them through the assistant, and confirm that each reply cites the right file and section. Google's developer documentation describes how the Drive API reads files with the owner's permission, and your administrator can confirm the sharing settings that apply. The check is about your documents, so it cannot be settled by documentation alone.
Can I start with part of a staff knowledge assistant on Google Workspace?
Yes. A sensible first stage covers one shared folder, such as the onboarding guide or the close checklist, and a small set of questions from the team. Once that answers reliably with sources, further folders can be added to the mapping list, and the connections to other Workspace areas can follow later. Each stage leaves a working tool in place, so staff are not waiting on a full build before they see any benefit.
How does MILabs test a staff knowledge assistant against Google Workspace?
MILabs tests the assistant under real working conditions. The test set is drawn from real questions and the folders you approved, and each answer is checked for the right source, the right section and whether the assistant stayed inside the scope rules. Access is tested with a staff account that has only its normal permissions, so a question about restricted material should return a refusal. Results are reviewed with your team lead before the tool is opened to everyone.
let's make something happen

Custom development: how we can help

Choose how you want to work on this with MILabs. Both options start with an enquiry.

Discovery is free, no obligation from the first chat.

Let us build it for you

We build it and look after it.

Build it yourself, we'll help

You build it with our direction, teaching and a weekly check-in.