A company knowledge assistant is only as dependable as the material it can retrieve and the rules around that material. Connecting a folder is the easy part. Deciding whether its contents are current, authorised and useful is the work that makes the connection worthwhile.
Start with one team and one repeated question set. This guide describes preparation for a knowledge pilot; it does not imply that connecting Google Workspace gives an assistant unrestricted access to every company file.
Choose one question set
A small operations team might start with questions about booking changes, handovers and escalation. A sales team might choose approved product facts and proposal templates. Avoid mixing payroll, legal disputes and ordinary operating instructions into the same first collection.
Write ten questions someone actually needs answered. For each, record the authoritative document and the answer a reviewer expects. Include a question that the documents cannot answer. A useful assistant should acknowledge that gap rather than fill it with a plausible guess.
Make a document register
Before importing anything, create a simple register with these fields:
- Title and source: where the original lives, including its link or document identifier.
- Owner: the person who can approve a correction.
- Last reviewed: when someone checked that the instructions still apply.
- Audience: who is permitted to use the information.
- Status: current, draft, superseded or archived.
If two files describe the same process differently, resolve that conflict first. File names such as “final”, “final-new” and “final-approved” are not a version policy. Keep one current source and a clearly separated archive.
Prepare documents for retrieval
Use descriptive headings, explain abbreviations and keep an instruction with its exceptions. A paragraph saying “approve requests under the usual limit” is difficult to use safely if the limit appears only in someone’s memory. State the limit in the source or mark that the answer needs a named approver.
Break large mixed-purpose documents into coherent sections. Preserve source references when creating extracts so a reviewer can find the original. Remove material you do not have permission to share with the chosen service. Redaction should happen before upload, not after an assistant has already processed the document.
Understand what the connection authorises
A Google sign-in verifies an identity. A Drive permission authorises particular access. An import or sync determines what content the application actually stores or processes. Those are different steps.
InriGPT’s organisation workflow includes Google Workspace connection and selected Drive document sync; the integration page describes the current scope. Review the consent screen and the documents selected for import. Do not assume that Google’s folder permissions automatically become a separate access policy inside another application.
Only add information suitable for the people who can use that organisation workspace. Before introducing more sensitive collections, confirm how member access, revocation and imported copies are handled. The privacy and data page is the starting point for InriGPT’s published handling information.
Run an answer review, not just a connection test
Successful authorisation proves that the connection completed. It does not prove that answers are correct. Ask the prepared questions and compare each answer with the approved source.
| Test | What the reviewer checks |
|---|---|
| A direct policy question | The answer preserves the relevant conditions and exceptions. |
| An outdated instruction | The current source is used; archived guidance is not presented as current. |
| An unanswered question | The assistant states the gap and directs the user to the document owner. |
| A requested action | A summary of a process is not misrepresented as approval to carry it out. |
Give the collection an owner after launch
Set a review cadence that fits how often the process changes. When a policy changes, update the original, refresh the imported material if needed, and rerun the affected questions. Keep a small log of wrong or incomplete answers so the next update addresses real problems.
For a first pilot, a short, maintained collection usually gives reviewers a clearer job than a large folder of uncurated files. Start with the workspace walkthrough and use the pilot worksheet to track review effort as well as successful answers.
