Connectors Overview
Connectors are CoreCube's automated ingestion path. They sync documents from external systems into the evidence layer through scheduled runs and manual triggers.
The three ingestion paths
All knowledge enters CoreCube through one of three paths:
| Path | Description | Source tag |
|---|---|---|
| Connectors | Automated delta sync from external systems | connector |
| Library | Manual document uploads (PDF, Markdown, DOCX, etc.) | library |
| Check-ins | Human knowledge via Slack, Teams, email, web form, or API | checkin |
All three converge into the same evidence layer with identical retrieval treatment. The source_path tag enables trust-aware ranking and scope filtering.
Available connectors
Purpose-built integrations with reliable incremental sync, deletion detection, and content normalization.
| Connector | Source | Change detection |
|---|---|---|
| Confluence | Atlassian Cloud spaces and pages | Page version number |
| Jira | Atlassian Cloud projects and issues | Issue updated timestamp |
| Local Files | A mounted local directory | Scan time + file metadata |
Each available connector provides:
- Stable external document IDs
- Incremental sync (only fetch changed documents)
- Deletion detection (tombstone documents when upstream deletes)
- Content normalization (HTML, ADF, PDF, DOCX → clean markdown)
Planned
Additional connectors are planned but not yet available: Notion, Microsoft 365, GitHub, GitLab, Bitbucket, Google Drive, Slack, HubSpot, and Nextcloud. An MCP-server connector — ingesting selected resources and read-only tools from an external MCP server — is coming soon.
Compartments and access control
Every connection belongs to exactly one compartment and has a sensitivity level. Together they form the connection's security label (e.g., hr/confidential).
Compartments
Admin-defined organizational boundaries — teams, departments, or functional areas:
executive rnd hr finance engineering legal all-staff
A connection's compartment cannot be changed after creation. To reclassify, delete and recreate the connection.
Sensitivity levels
| Level | Description | Example |
|---|---|---|
public | Safe for anyone in the organization | Public docs, marketing |
internal | General internal, not externally shareable | Team wikis, project docs |
confidential | Sensitive, restricted access | Financial reports, HR records |
restricted | Highly sensitive, need-to-know | M&A docs, legal matters |
Source filtering
First-class connectors support filtering at connection setup so you can create narrow, compartment-appropriate connections instead of one broad connection:
✓ "Confluence — Engineering Docs" compartment: engineering sensitivity: internal
Space keys: ENG, DEVOPS
✓ "Confluence — HR Policies" compartment: hr sensitivity: confidential
Space keys: HR
✓ "Confluence — Company Handbook" compartment: all-staff sensitivity: public
Space keys: HANDBOOK
The connection form surfaces these filters prominently with a guidance message: "Select which parts of this source to ingest. Create separate connections for content with different sensitivity levels."
Source trust levels
| Trust level | Description | Example sources |
|---|---|---|
| Authoritative | Official, maintained documentation | Runbooks, approved policies, official docs |
| Reference | Useful context that may be informal | Wiki pages, shared notes, meeting summaries |
| Volatile | Rapidly changing or unverified | Chat exports, draft documents, ticket comments |
Default: reference. Trust level is used as a tie-breaker in search ranking when chunk scores are equal.
Sync schedule
Each connection has a configurable sync interval (e.g., every 15 minutes, every hour, daily).
Manual sync: Click Sync Now in the connection detail view to trigger an immediate sync.
Connection health
The Admin Console shows real-time connection health:
| Status | Meaning |
|---|---|
| Healthy | Last sync completed within the expected window |
| Degraded | Last sync had partial failures or is overdue |
| Offline | Cannot reach the source or authentication failed |
Connector metrics
Per-connection metrics available in the connection detail view:
| Metric | Description |
|---|---|
documents_found | Total documents discovered during the sync |
documents_new | Newly ingested documents |
documents_updated | Existing documents re-ingested after a change |
documents_skipped | Unchanged documents not re-processed |
documents_failed | Documents that failed extraction or ingestion |
chunks_created | Evidence chunks created during the sync |
chunks_deleted | Evidence chunks removed during the sync |
status | Sync outcome: completed, partial_ok, or failed |
trigger_type | What started the sync: scheduled or manual |
error_message | Most recent error summary, if any |
error_details | Structured per-document error details |
Resource limits
| Resource | Limit | Behavior when exceeded |
|---|---|---|
| Document content size | 50 MB raw | Document fails and is counted in documents_failed; the sync continues |