Skip to content

Knowledge Documents

Knowledge Documents are the place to put the business knowledge that doesn’t live in rows and columns—taxonomies, campaign-naming conventions, brand voice, KPI definitions, partner contracts, glossaries. Once attached, Aliveo AI consults them in Analytics Chat and Automation Agents to better understand your business.

If you can paste it into a Doc or a Sheet, you can put it in front of the AI.

What You Can Attach

Format Use it for
Google Doc Long-form prose: strategy briefs, brand books, naming conventions
Google Sheet Lookups and taxonomies: market codes, audience definitions, KPI mapping tables
CSV Same as Sheets, when you’d rather upload a static snapshot
Custom text (inline) Short notes you don’t want to keep in a separate file

You can attach as many documents as you like. Aliveo will pull only the ones that are relevant to the question being asked at runtime.

Scoping Documents

Each document is scoped to one of three levels:

  • Global — applies organization-wide. Good for company glossaries, brand books, KPI charters.
  • Business — applies to a single line of business. Good for LoB-specific playbooks.
  • Account — applies to a single connected ad account or data source. Good for account-specific contracts, market mappings, or audience definitions.

Documents inherit downward (Global is visible from every business and every account; Business is visible from every account inside that business). Account-attached documents stay account-scoped.

Attaching a Document

Global documents

  1. Open My Account → Global Documents.
  2. Click Connect Document.
  3. Choose Google Doc, Google Sheet, CSV, or Custom Text.
  4. Paste the URL (for Google Docs/Sheets), upload the file (for CSV), or type your text inline.
  5. Grant Aliveo’s service account view access if prompted.
  6. Add a title and a short description explaining what’s inside.
  7. Save.

Business-scoped documents

  1. Open My Account → select a business.
  2. Open the Connected Documents tab (or scroll down on the business page).
  3. Follow the same Connect-Document flow above. The document will only apply within the active business.

Account-scoped documents

  1. Open My Account → select a business → pick an account card.
  2. Open the Account Context tab.
  3. Under Connected Documents, click Connect. Documents you attach here can also be reused across other accounts within the same business via the Applies to these accounts selector.

Viewing and Editing

For each knowledge document you can:

  • Preview content — view what Aliveo is actually reading.
  • Rename — give it a clearer title without re-uploading.
  • Update custom text — for inline custom-text documents, edit directly inside Aliveo.
  • Re-fetch — pull the latest version from Google Docs/Sheets.
  • Detach — remove it from this scope (the underlying file in Drive is untouched).

How Documents Get Used

Documents are not blindly stuffed into every prompt. Aliveo:

  1. Determines what the user is asking and which accounts are in scope.
  2. Selects the documents whose scope and topic match the question.
  3. Reads the relevant portions and grounds the response in them.

In Analytics Chat and Automation Agents, document selection is automatic—based on the active scope and the question content.

Best Practices

  • Use real titles and descriptions. “Brand Voice Guide v3 (Q2 2026)” beats “Untitled Sheet (1).”
  • One concept per document. Smaller, focused docs are picked up more reliably than 200-page mega-docs.
  • Tables work best as Sheets. If your document is a lookup table (market codes, audience IDs), put it in a Sheet, not a Doc.
  • Scope intentionally. Don’t attach an account-specific doc globally—the resolver will surface it for accounts where it doesn’t apply.
  • Refresh after big changes. When a Google Doc or Sheet has materially changed, hit Re-fetch to pull the latest copy.

A Note on Security

Aliveo accesses Google Docs and Sheets via OAuth using the service account that you grant view access to. No credentials are stored. CSV uploads and custom text are encrypted at rest in your organization’s storage (see Security and Privacy).