Google Drive
OAuth connection, scoped folders, incremental changes, originals, and source permissions.
Modular integrations
Use the internal wiki, authorize a supported provider, or connect private infrastructure. Every source enters one permission-aware indexing and evidence path.
Internal wikiCloud sourcesPrivate infrastructure
Supported source boundaries
Each connector owns authentication, discovery, change detection, scope selection, original-file access, and provider ACL translation. Shared ingestion services handle processing, indexing, and repair.
OAuth connection, scoped folders, incremental changes, originals, and source permissions.
Bring Microsoft 365 document libraries into the same governed retrieval boundary.
Index message threads, participants, dates, attachments, and linked customer context.
Connect self-hosted file storage through a dedicated provider implementation.
Index managed network storage while keeping content behind the CogLake API boundary.
Discover files on private systems through scoped service credentials and controlled paths.
Expose authorized evidence and originals to agents, applications, and automation tools.
Enterprise connector development reuses the same tested contracts for identity, checkpoints, retries, content, and ACLs.
Operational by design
Choose a supported authentication method, test the connection, and define allow or deny scopes before sync starts.
Stable source IDs and checkpoints limit updates to changed and deleted documents instead of rebuilding the corpus.
Source principals and role overrides remain attached through search, preview, download, graph, MCP, and REST.
Knowledgebase connectors synchronize source content. In AI Workspace, connected MCPs expose tools and resources; skills supply task-specific instructions. Discover personal or company resources under central policy.
Start with your real knowledge
We will review authentication, data volume, permissions, and change behavior before the first production sync.
Book a walkthrough