Step 1 of 15 · Intro

Design enterprise search with permissions

Employees search and ask across documents, tickets and chat, each source with its own access rules. Filter by permission before the model, then size indexes, cache and models within a budget.

How it works

• ›Sync: connectors read changes (edits, deletes and permission changes) incrementally and put them on a queue.
• ›Index: workers split content into chunks, embed them, and write each chunk with its allowed principals to the keyword and vector indexes.
• ›Retrieve: the asker's principals are applied as a filter inside both index queries; the reranker keeps the best few.
• ›Answer: the model sees only permitted passages and cites them; a cache keyed by permission scope saves repeat work.

What you'll build

1. The API and the connector, document, chunk and membership data
2. The question path and the ingestion path with fan-out to two indexes
3. A permission-scoped cache, and a budget
4. A lost search node, a provider outage, a cold cache, and the full peak
5. Deep dives: filtering in the index, connectors and deletes, revocation lag, cache leaks, shared semantic caches