> ## Documentation Index
> Fetch the complete documentation index at: https://docs.endgame.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Upload Knowledge

> Add your sales methodology, battlecards, and playbooks to shape how Endgame thinks

<Info>
  [Implementation Guide](/implementation-guide/overview) · Module 4 of 9 · \~10 minutes
</Info>

## Why this matters

Knowledge is what transforms Endgame from a data lookup tool into something that reasons like your best reps. When a user asks "How should I position against Competitor X?", Endgame pulls from your competitive battlecards. When they ask for a deal inspection, Endgame applies your qualification methodology. Without knowledge, Endgame still works with your CRM and call data, but it won't reflect how *your team* thinks about selling.

## What you'll do

* Identify your top 3-5 knowledge documents to upload first
* Upload them to Endgame via your preferred method
* Understand sync behavior for different source types

## What to upload first

Think about what you'd hand a new rep in their first week. These five categories cover the most ground:

1. **Sales methodology guide**: Your MEDDIC, BANT, or custom framework. Even a one-pager describing how your team qualifies deals is valuable.
2. **Competitive battlecards**: Positioning against your top 3-5 competitors. Basic notes are fine.
3. **Persona playbooks**: How to engage different buyer roles. Your website's buyer personas might be enough.
4. **Product messaging**: Core positioning and value props. Your website often covers this well.
5. **Discovery or demo framework**: Your proven questions and talk tracks. A bulleted list works.

<Tip>
  Don't overthink it. A simple one-pager beats nothing. And you don't need all five categories to get started. Even one good methodology doc makes a difference in response quality. You can always add more later.
</Tip>

## Walkthrough

<Steps>
  <Step title="Navigate to Knowledge settings">
    Go to [Settings > Knowledge](https://app.endgame.io/settings/knowledge). This is the unified view of all knowledge across your organization.
  </Step>

  <Step title="Choose your upload method">
    Click **Add Files** and choose from three options:

    **Upload from device** - Best for files you have locally. Select up to 10 files at a time. You can edit titles and descriptions before uploading.

    **Link from Google Drive** - Best if your enablement content lives in Google Drive. Authenticate with Google, then select files. These auto-sync once per day, so updates to the source files will be reflected in Endgame.

    **Import from public URL** - Best for content that lives on your website (pricing pages, product positioning, case studies). Paste the URL and Endgame will ingest the page content.
  </Step>

  <Step title="Connect knowledge sources for automatic sync">
    For content that changes regularly, connect a knowledge source so Endgame stays current without manual re-uploads. Navigate to [Settings > Integrations](https://app.endgame.io/settings/integrations) and connect any of the following:

    **Google Drive** - Authenticate with Google and select specific files or folders. Endgame syncs changes once per day, so when your team updates a battlecard or methodology doc, the latest version flows into Endgame automatically.

    **Notion** - Connect your Notion workspace and select the pages or databases that contain enablement content. Endgame syncs updates every hour, making Notion a great home for living documents like competitive intel or process guides that evolve over time.

    **SharePoint** - Connect your SharePoint site to pull in documents from libraries your team already uses. Endgame syncs changes every 15 minutes, making it ideal for orgs that manage enablement content in Microsoft 365.

    **Confluence** - Connect your Confluence workspace and select the spaces or pages that hold your team's knowledge. Endgame syncs changes once per hour, making it one of the fastest sources to reflect updates.

    **Snowflake** - Connect your Snowflake instance to bring in structured data from tables, views, or dynamic tables. Endgame queries your Snowflake data once per hour and includes those insights in chat responses. This is useful for syncing operational data like usage metrics, health scores, or custom reporting that lives in your data warehouse. Note that Snowflake data is treated as organization-level knowledge, not account-specific.

    <Tip>
      Connecting a knowledge source is a best practice. Rather than uploading static files that go stale, linking to where your team already maintains content means Endgame picks up changes as they happen. Start with whichever platform holds the majority of your enablement content.
    </Tip>
  </Step>

  <Step title="Review auto-categorization">
    After uploading, Endgame automatically categorizes documents as organization-level or account-specific and detects account associations. This can take a few minutes. You can edit associations manually if needed.
  </Step>
</Steps>

## Sync behavior

| Source        | Auto-sync     | Manual sync                    |
| ------------- | ------------- | ------------------------------ |
| Google Drive  | Once per day  | Available anytime              |
| Notion        | Once per hour | Available anytime              |
| SharePoint    | Every 15 min  | Available anytime              |
| Confluence    | Once per hour | Available anytime              |
| Snowflake     | Once per hour | Available anytime              |
| Public URL    | No auto-sync  | Must trigger manually          |
| Device upload | No sync       | Must re-upload for new content |

If your enablement content changes frequently, connecting a knowledge source like Google Drive, Notion, SharePoint, Confluence, or Snowflake is better than device uploads since they stay current automatically.

## Quality over quantity

Resist the urge to upload everything. Outdated battlecards, deprecated process docs, or conflicting methodology guides create noise. The principle: if you wouldn't want a new rep using it tomorrow, don't give it to Endgame. A small set of excellent, current materials beats a large library of mixed quality.

## Checkpoint

You've completed this module when you've uploaded at least one knowledge document. You'll see it listed in the Knowledge settings view. You'll validate its impact in Module 7 (Test Drive) by asking questions that should reference the content you uploaded.

## Go deeper

* [Knowledge Basics for Admins](/knowledge/knowledge-basics-for-admins) for detailed guidance on what to connect
* [Import Documents](/knowledge/file-upload) for the full reference on upload methods and management
* [Google Drive Troubleshooting](/knowledge/google-drive-troubleshooting) if you hit issues with Google Workspace

***

<Columns cols={2}>
  <Column>
    <Card icon="arrow-big-left" horizontal href="implementation-guide/connect-slack" title="Previous Module">
      Connect Chat
    </Card>
  </Column>

  <Column>
    <Card icon="arrow-big-right" horizontal href="implementation-guide/create-first-rule" title="Next Module">
      Create Your First Rule
    </Card>
  </Column>
</Columns>