top of page
Typing

How Good Bards Marketing OS Gives Your Team Full Control Over What AI Knows

The New Question Every Marketing Team Is Asking


When a company adopts an AI-powered marketing platform, the first question is almost always: "What can the AI do?" The smarter question — the one that separates teams that get results from teams that get frustrated — is: "What does the AI know, and how do we control it?"


This is the data access problem. And in an era where marketing teams are moving from prompt-based chatbots to fully agentic AI that reasons, decides, and executes tasks autonomously, how your AI accesses information is no longer a back-end technicality. It is a core part of your marketing operations strategy.


Good Bards Marketing OS — an all-in-one AI-powered marketing platform for teams — is built with this challenge in mind. Its approach to data access is deliberate, layered, and designed to work for both the lean agility of an SME and the structured governance demands of an enterprise.


The Foundation: Good Bards Drive


Every data access method in Good Bards Marketing OS begins with Drive — the platform's built-in storage layer. Drive is where your team uploads, organises, and manages the files that your AI agents will draw from: brand guidelines, campaign briefs, product catalogues, research reports, compliance documents, and more.


What makes Drive central to the Good Bards experience is its tenant architecture. When a file is uploaded to Drive, every user within the same tenant — your organisation's workspace — can access it. For larger organisations operating across divisions or regions, Drive also supports sub-tenant sharing, allowing controlled distribution of files to sub-groups without opening access to the entire organisation.


This shared foundation matters because it means your AI agents are not working in isolation. When data is in Drive, it is organisationally available — not siloed to the person who uploaded it.


Three Ways to Give Your AI Access to Data


Good Bards Marketing OS offers three distinct methods for making information available to its agentic AI. Each one serves a different operational need, workflow, and level of deliberate control.


Method 1: Upload to Drive and Enable RAG


What it is: Retrieval-Augmented Generation (RAG) is the method by which an AI agent automatically retrieves relevant context from a file before generating a response. In Good Bards, enabling this is as simple as toggling the AI switch on any file stored in Drive. Once toggled on, any agent with RAG enabled will automatically consult that file before responding — every time, without any user intervention required.


Best for: Evergreen, always-relevant content that every agent should know about. Think brand voice guidelines, approved messaging frameworks, product feature lists, pricing structures, or company-wide tone-of-voice documents.


SME use case: A small marketing team uploads their brand guidelines and product FAQs to Drive and switches on RAG. Every AI agent they deploy — whether for social content, email copy, or ad creative — automatically draws from these files. The team writes fewer correction prompts and spends less time fixing off-brand output.


Enterprise use case: A regional marketing enterprise uploads its master messaging matrix and compliance-cleared claim library. With RAG enabled across agents, every content output — regardless of which team member triggered it — is grounded in approved, up-to-date corporate information. This significantly reduces brand governance risk at scale.


Pros:

  • Always-on: no manual action needed per conversation

  • Scalable across all agents and all team members

  • Consistent grounding — AI always checks before responding

  • Tenant-wide and sub-tenant sharing means one upload serves many users

Cons:

  • Less surgical — the AI retrieves from these files even when they may not be directly relevant to a specific task

  • Requires active file management to ensure RAG-enabled files are current

  • Not suited to confidential or session-specific information


Method 2: Upload to Drive and Access via the Knowledge Base Tool


What it is: The Knowledge Base tool allows an AI agent to access a specific file from Drive when a user — or the agent itself — deliberately directs it to do so. Unlike RAG, this method is not automatic. The agent only reads the file when the Knowledge Base tool is invoked in a given conversation, and that access is scoped to that session only.


Best for: Targeted, on-demand reference tasks where the user knows exactly which document the AI needs to consult. Campaign performance reports, competitor analysis documents, creative briefs, research summaries, or region-specific guidelines are all strong candidates.


SME use case: A content manager uploads a detailed client brief to Drive before kicking off a campaign. When working with the AI agent on copy, they direct it to pull from that brief using the Knowledge Base tool. The agent reads it, uses it in context, and the session ends. The file stays in Drive for future reference, but is not permanently active in every AI interaction.


Enterprise use case: A compliance team maintains a library of regional regulatory documents in Drive. Agents with the Knowledge Base tool enabled can be directed to consult the relevant regional document when generating claims or messaging for a specific market — providing precision without making sensitive regulatory content a permanent part of every AI session.


Pros:

  • Precise and intentional — the AI only reads what it needs, when it needs it

  • Accessible to any agent with the tool enabled

  • Files remain centrally managed in Drive without being always-on

  • Useful for structured, document-heavy workflows

Cons:

  • Requires the user to know which file is relevant — not ideal for exploratory or open-ended tasks

  • Access is session-scoped; the AI does not carry learnings into future conversations

  • Relies on good Drive organisation so files can be identified and directed to efficiently


Method 3: Upload a File Directly Into a Chat Session


What it is: The most immediate and flexible method. When initiating an agentic chat session in Good Bards, a user can upload a file directly into the conversation. The file is then available to the AI for that session. Source flexibility is built in: the file can come from a local drive, Google Drive, or other file storages.


Best for: One-off, ad hoc tasks involving files that are external, confidential, or not yet appropriate for shared Drive storage. A supplier proposal just received by email. A client-provided brief. A raw data export from a third-party tool. Any document the user has on hand and needs to act on immediately.


SME use case: A founder receives a competitor's pricing document and uploads it directly into a Good Bards chat session. Without needing to organise or store it, they ask the AI agent to analyse pricing gaps and draft a response strategy. The session ends; the file is not retained in the platform.


Enterprise use case: A strategist needs to review a confidential M&A background document that cannot be stored on shared infrastructure. They upload it directly from their local drive into a session, run the analysis, and the file does not enter the broader tenant Drive. This preserves data governance boundaries while still leveraging AI capability.


Pros:

  • Fastest path from file to AI action — no pre-uploading or organisation required

  • Works across local drives, Google Drive, and Box — meeting users where their files already live

  • Ideal for sensitive or temporary files that should not persist in shared storage

  • No dependency on Drive organisation or team workflow setup

Cons:

  • The user must have the file in their possession — cannot pull from a shared library

  • Not scalable for team-wide use; access is exclusive to the user who uploads it

  • No persistent organisational value — the file does not contribute to your shared knowledge base

  • Best for individuals, not coordinated team workflows


SME vs Enterprise: Which Method Fits Your Team?


There is no single correct answer — but there is a pattern worth noting.


SMEs tend to benefit most from a hybrid of RAG and direct upload. RAG handles the evergreen organisational knowledge (brand, product, tone) once and serves it automatically. Direct upload handles the fluid, fast-moving, often external documents that characterise the day-to-day of a small, agile team. The Knowledge Base tool becomes valuable as the team grows and develops more structured document libraries.


Enterprises typically require all three methods operating in concert. RAG enforces brand and compliance standards at scale. The Knowledge Base tool enables precision access to structured reference documents — by region, product line, or market — without cluttering every agent session. Direct upload preserves the ability to handle sensitive, confidential, or externally sourced content without compromising data governance frameworks. The sub-tenant sharing feature in Drive adds another layer of control for divisional or regional structures.


Why This Matters Now: Agentic AI Changes Everything


Most organisations are still thinking about AI in terms of prompts and responses — a human asks, the AI answers. Agentic AI is fundamentally different. Agents plan, execute multi-step tasks, make decisions, and operate with increasing autonomy. As this shift accelerates, what your AI knows is as important as what it can do.


An agent that always draws from accurate, current brand guidelines produces better output than one prompted from scratch every session. An agent that can precisely access the right research document is more reliable than one guessing from general knowledge. An agent that can handle a confidential document in an isolated session is one that an enterprise compliance team can actually approve for use.

This is the design philosophy behind Good Bards Marketing OS's approach to data access: not one method for all situations, but the right method for each one.


The teams — whether a five-person SME or a five-hundred-person enterprise — that invest in understanding how their AI accesses data will be the ones that unlock consistent, scalable, trustworthy AI-powered marketing. The others will keep wondering why their AI keeps getting the brand voice wrong.


Good Bards Marketing OS — Data Access Methods: Pros & Cons

Method

Pros

Cons

Method 1

Drive + RAG toggle

✓  Always-on — no action needed per session

✓  Scales across all agents and team members

✓  Consistent grounding before every AI response

✓  Tenant-wide access; shareable with sub-tenants

✓  Ideal for evergreen content — brand, product, tone

✗  Less precise — AI retrieves even when not relevant

✗  Requires active file management to stay current

✗  Not suitable for confidential or session-specific files

✗  May slow response if RAG pulls from large file sets

Method 2

Drive + Knowledge Base tool

✓  Intentional and precise — AI reads only what's directed

✓  Any agent with the tool enabled can access the file

✓  Files stay centrally managed without being always-on

✓  Great for structured reference: briefs, reports, research

✓  Session-scoped access supports focus and privacy

✗  User must know which specific file to reference

✗  Requires deliberate action — not automated

✗  Access ends when the conversation ends — no persistence

✗  Depends on well-organised Drive for efficient retrieval

Method 3

Direct upload to chat

✓  Fastest path from file to AI action — no pre-upload needed

✓  Supports local drive, Google Drive, and Box.com

✓  Ideal for sensitive files that shouldn't enter shared Drive

✓  No dependency on Drive structure or team workflow

✓  Flexible for one-off, ad hoc, or external documents

✗  User must have the file in their possession to upload

✗  Not scalable — one user, one session at a time

✗  No team access — only the uploader can use the file

✗  Adds no lasting value to the shared knowledge base



Frequently Asked Questions


What is Good Bards Drive? Drive is the built-in file storage feature in Good Bards Marketing OS. It serves as the central repository from which AI agents can access information. Files stored in Drive are accessible to all users within a tenant and can be shared with sub-tenants.


What is RAG in Good Bards Marketing OS? RAG (Retrieval-Augmented Generation) is a method by which an AI agent automatically retrieves relevant content from a file before generating a response. In Good Bards, users enable RAG for a file by toggling the AI switch within Drive. Any agent with RAG turned on will consult those files before every response.


What is the Knowledge Base tool in Good Bards? The Knowledge Base tool allows users to direct an AI agent to read a specific file from Drive during a conversation. Unlike RAG, this access is intentional and session-scoped — the AI reads the file when explicitly directed to, and access ends when the conversation ends.


Can I upload a file from Google Drive or Box into Good Bards? Yes. When uploading a file directly into a Good Bards chat session, you can source it from your local drive, Google Drive, or Box.com — giving you flexibility regardless of where your files are stored.


Which data access method is best for an SME? SMEs typically benefit most from combining RAG (for always-on brand and product knowledge) with direct upload (for ad hoc, external, or client-provided documents). The Knowledge Base tool becomes increasingly useful as the team builds a more structured document library.


How does Good Bards support enterprise data governance? Good Bards supports enterprise governance through its tenant and sub-tenant architecture in Drive, its session-scoped Knowledge Base tool that limits access to active conversations, and the ability to upload sensitive documents directly into a session without storing them in shared infrastructure.


What is the difference between RAG and the Knowledge Base tool? RAG is automatic and always-on: the AI checks RAG-enabled files before every response without any user instruction. The Knowledge Base tool is intentional and session-specific: the user directs the AI to a particular file during a conversation, and access ends when the session ends.


Ready to Put Your Data to Work?


Good Bards Marketing OS gives marketing teams — at every size and stage — the infrastructure to deploy agentic AI with confidence. Whether you are an SME looking to scale consistent output or an enterprise managing brand governance across teams and regions, the right data access strategy starts with the right platform.


Comments


Commenting on this post isn't available anymore. Contact the site owner for more info.
bottom of page