Uploads vs. Connectors: Two Paths to Knowledge
CoreManage uploaded knowledge and connectors · Difficulty 1/5
Explanation
Two Ways Knowledge Reaches Claude
| Path | What it is | Example |
|---|---|---|
| Upload | A file added directly, becoming Project or conversation knowledge | A PDF policy document, a spreadsheet, a slide deck |
| Connector | An integration to an external source, letting Claude work with content where it already lives | Google Drive, Gmail |
Uploads are static snapshots -- the file as it existed at the moment you added it. Connectors instead point at a live source, so Claude works with content in its original location rather than a copy someone had to export and attach.
Availability Is Plan-Dependent
Which Connectors and related features are available is tied to the plan/pricing tier -- it is not a universal capability every account has by default. A business user configuring knowledge sources needs to check what their tier actually supports rather than assuming every integration is available.
Common exam traps
- **Assuming all Connectors are available on every plan.** Availability is tier-dependent; an exam item that implies a connector is universally available is testing this exact misconception.
- Confusing an upload with a connector, or treating the two as interchangeable -- an upload is a file you added; a connector is a live link to an external source, and the distinction matters for staleness (see the related concept on curation and governance).
Key Takeaways
- Uploads are files added directly; connectors integrate live external sources such as Google Drive or Gmail
- Connectors let Claude work with content where it already lives, rather than requiring an exported copy
- Connector and feature availability depends on the plan/pricing tier, not a universal default
- Assuming every connector is available on every plan is a common exam trap
Glossary Terms
Integrations that let Claude work with content in an external source (e.g., Google Drive, Gmail) where it already lives, rather than requiring a manually exported and uploaded copy. Distinct from uploads (static files added directly); connector availability depends on the plan/pricing tier and is not universal.
A persistent workspace in claude.ai that bundles standing Instructions (role, tone, format, rules) and Project Knowledge (uploaded reference documents) so every conversation inside it draws on the same configuration without re-supplying it each time. Scales beyond a single context window because large Project Knowledge is retrieved rather than loaded in full on every turn.
Related Concepts
Projects as a Persistent Workspace
A Project bundles standing instructions (role, tone, format, rules) and project knowledge (uploaded reference material)
Curating Knowledge Sources and Governance Overlap
Curating knowledge means adding what matters, keeping it organized, and removing or updating stale material