Company Wiki

A living map of what your company knows.

The policy and context layer that every agent team reads from - connect Notion, Confluence, or Google Drive to keep every team current.

Connected knowledge

Map structure without migrating a single file.

OAuth connectors sync Notion, Confluence, Drive, and SharePoint into vaults your agent teams can cite.

Company Wiki file tree and knowledge graph view

Connect where knowledge already lives.

Point Nimbus at your existing storage - no engineering project, no brittle sync scripts.

Wiki semantic search across connected vaults

Semantic search across vaults.

Ask in natural language and retrieve passages grounded in your documents - not generic web priors.

No migration

OAuth in minutes. Always in sync.

Connectors pick up edits as teams publish - folders, vaults, and paths map from your source hierarchy automatically.

  • OAuth in minutesConnect existing storage with standard OAuth - no engineering project, no brittle sync scripts.
  • Always in syncConnector refreshes pick up edits as teams publish - no manual re-upload or duplicate copies.
Company Wiki document view with connected vault graph
Connected knowledge

Every department draws from the same source.

The Company Wiki is the document view of your Lifecycle Graph - files link to concepts, owners, tags, and workstreams.

Wikilinks and relationships

Pages link to related policies, owners, and workstreams - not isolated files in disconnected drives.

Semantic search

Ask in natural language and retrieve the passages that matter - grounded in your vaults.

Backed by the Lifecycle Graph

Documents connect to runs, approvals, and outcomes - so context compounds instead of resetting.

Playbooks that stay current

When a connector syncs or a workstream lands a decision, the wiki view updates for every downstream team.

Living map

Institutional knowledge that stays when people leave.

When employees move on, their expertise should not walk out the door. The Wiki captures it and makes it available to every department.

Current & governed

Versioned, scoped, and approval-aware.

Wiki content feeds runs with the policy version that applied at decision time. Sensitive vaults stay role-scoped.

Version at decision time

Decision History records which policy revision grounded each run - not whatever is live today.

Role-scoped vaults

Finance policies stay in Finance vaults. Sales never sees HR compensation docs unless you scope it.

Agent scope controls

Each swarm declares which vault prefixes it may retrieve - retrieval respects workspace boundaries.

Approval-aware context

High-risk runs can require policy sign-off before writes execute.

Auto-refresh from sources

Connector-synced pages refresh on a schedule so agent teams never reason over stale documentation.

Audit-ready access

Who read which vault, when, and for which workstream - without reconstructing access from chat exports.

Better together

Knowledge that powers your whole ecosystem.

Wiki, agent teams, perception, and governance share the same source of truth.

Agent Teams read it

Every department grounds analysis in your current policies and playbooks from day one.

Explore Agent Teams

Perception searches it

Ask a question in plain English and get answers cited from your real documents and vaults.

Explore Perception

Governance gates it

Sensitive material stays role-scoped; every retrieval and write path is logged and approval-aware.

Explore Governance

Build the knowledge layer that stays when people leave.

Connect your storage and Nimbus maps your knowledge automatically.