Document
enhanced_diagrams/) — here, or
browse.
Google Docs
Metadata
Off = images indexed with their alt text (cheaper, current default).
Crawl a website into the knowledge base
The crawl runs, AI curates & auto-categorizes the pages, then they wait for your approval below — nothing is ingested automatically.
Auto-sorts pages into categories & scores quality (uses your OpenAI key).
Crawl progress
Review & approve
crawled pages, auto-sorted into categories — expand a category, click a page for details, and approve. Nothing is ingested until you approve.Pipeline
live · refreshes automaticallyKnowledge base
| Document | Type | Domain | Access | Review | Quality | Chunks | Entities | Relations | Images |
|---|
Recently deleted
Deleting is soft: the ledger keeps every row, so a restored document returns exactly as it was — entities, relations, images and merges fold back byte-identical. Restoring re-embeds its search vectors (a few cents).
| Document | Domain | Deleted at | Chunks | Entities |
|---|
Access control
Documents carry tags; people are granted tags; a person sees a document when their tags overlap its tags. Admins always see everything. Nothing is enforced yet — tags are being recorded now so that turning enforcement on later is a switch, not a migration.
Tags
| Tag | Part of | Docs | People |
|---|
People
Click a tag to grant or revoke it for that person. Somebody can belong to two departments — both are listed, and the primary one is only the default the ingest picker starts on. Setting it changes nothing anyone can read; manages is the one that does, because authority reads everything beneath.
Snapshots
A snapshot pins the whole knowledge base at this moment under a name — nothing is copied, the ledger already keeps every version. Any entity or document can be read as it stood at a snapshot via the as-of API.
| Name | Seq | Pinned | By | Note |
|---|
Synced Google Docs
Tracked Google Docs re-ingest automatically when their content changes — an unchanged doc is skipped for ~$0. Use Sync now to check one on demand.
| Document | Last synced | Version | Status |
|---|
Chats
Conversations synced from a connected account. A chat is not a file — it has a roster, a date range and a speaker on every line — so it gets its own view. One chat is one document, however many of its members connect.
No chats have been synced yet. Connect an account under Connectors and turn sync on.
Outlook threads synced from a connected account. Mail is opt-in by correspondent: nothing is read or ingested unless you tick the person, and every thread stays readable by its mailbox owners alone. One thread is one document, however many of its participants connect.
No mail has been synced yet. Turn on Outlook mail under Connectors, then choose which correspondents to ingest.
Your Claude, connected
A personal connector lets your own Claude search and ask this knowledge base as you — it sees exactly the documents your account can see, nothing more. Create one, add it to Claude, done.
New connector
The credential is shown once, right here — it is never stored on the server and cannot be shown again. Treat it like a password.
Your connectors
| Label | Credential | Created | Expires | Last used |
|---|---|---|---|---|
| none yet | ||||
Organisation ingestion connector admin
This is the credential the ingestion account's Claude uses to drain the sync queue and ingest everyone's connected chats. It is not a personal connector: it speaks for the organisation, not for you, and it can read every connected user's staged mail and chat before any of it is filed.
Link it to one Claude account — the organisation's ingestion account. It is refused on the personal endpoint, and a personal connector is refused on this one, so the two cannot be mixed up.
Shown once. A second one is a second key to the same door — revoke what you replace.
| Label | Credential | Created | Expires | Last used |
|---|---|---|---|---|
| none yet | ||||
App connectors
Connect your accounts — Gmail, Drive, Teams, Microsoft 365, ClickUp, Odoo — the same way connectors work in Claude. The ingest agent (coming next) will only ever act through the permissions you set here: read is on by default, write is off until you turn it on, and disconnect kills the credential.
loading…
Connect
Credentials are encrypted at rest and never shown again. The connection is verified live before it is saved.
Graph editor
Correct or remove what extraction produced. Edits write straight to the knowledge graph and re-sync Neo4j; retrieval picks them up automatically. Renaming an entity keeps its old name as an alias so existing queries still match. Adding brand-new nodes or edges isn't offered here — answers are only trusted when grounded in a document quote.
| Entity | Type | Description | Rels | Docs |
|---|
| Source | Relation | Target | Type | Docs |
|---|
Usage & cost
last 30 daysDaily spend
Estimated from token usage × a per-model price table — not a billing figure.
Neither OpenAI nor Gemini exposes a remaining-credit balance through an API key, so this shows
our metered spend for ingestion (extraction, resolution, embeddings). Calibrate the price table
to your real rates via the PRICE_TABLE_JSON environment variable.
Org
Who can read what
A person reads their own node and everything above it — that is membership, and it is automatic. Reading below a node is a manager privilege and must be granted deliberately. Projects sit outside the tree: membership is by grant only, so they cross departments. A document can carry several tags at once.
Policy
Org-wide rules that govern what the knowledge base may do — who can read what, and what mass ingestion is allowed to produce. Admin-only; every change is recorded in the ledger with who made it.
Access
API keys
Create a key
A new key may query and nothing else. Tick only what this integration genuinely needs — a key that shares no resources still gets grounded, verified answers, just without the material behind them.
key:<name>), so it must be unique.Copy this secret now — this is the only time it is shown
This kb_… value is the key itself:
the one thing an integration authenticates with. Only its SHA-256 is
stored, so it can never be displayed again. Lose it and the key must
be rotated for a new one.
Existing keys
Click a key to configure what it can do and what it may see.
Users
Add a user
Admins can add domains, delete documents and manage users. A normal user may ingest into existing domains and view the graph.
| User | Role | Created |
|---|