Back to releases
v1.6.0

Per-member knowledge-base grants — one workspace, different people, different knowledge (v1.6.0)

Admins can now restrict a member's knowledge-base visibility to a selected set — product manuals, legal contracts and meeting notes can live in one workspace while staying visible only to the right people. Out-of-scope access always returns 404 with no existence leak; admins and owners are unaffected; programmatic access (API keys / MCP) behaves exactly as before.

Access controlMulti-tenancyWeb ConsoleREST

Langhuan’s isolation unit has always been the workspace: workspaces are isolated from each other, but inside a workspace there were no boundaries — every member could see every knowledge base. When product manuals, legal contracts and meeting notes share one workspace, the only workaround was splitting into multiple workspaces, duplicating model configuration, retrieval settings and member management. v1.6.0 moves the answer to a finer grain: admins can restrict a member to a selected set of knowledge bases.

Where to configure it

The members page gains a “Knowledge bases” column (All / N knowledge bases). A member row now has a “Knowledge base access” action (visible to admins and owners): choose “All knowledge bases” or “Selected knowledge bases only”, the latter via a checkbox list — checking none means the member temporarily sees nothing. The programmatic equivalent is PUT /workspaces/:slug/members/:user_id/kb-grants.

The boundary rules, in four lines

  • Members only: admins and owners implicitly see everything — the management surface must show the whole picture, and the API refuses to set a restricted scope for them, preventing confusing “configured but ineffective” states.
  • Out of scope = doesn’t exist: ungranted knowledge bases disappear from listings and search pickers; visiting their URLs or calling the API with a hand-typed ID returns the exact same 404 as a nonexistent knowledge base — no existence leak.
  • Builders see their own: when a restricted member creates a knowledge base, it automatically enters their visible set — no “created it and can’t see it” trap.
  • Open by default, tighten on demand: new members start with full visibility; admins tighten afterwards. Existing members see zero behavior change after upgrading.

Programmatic access and retrieval are untouched

API key / MCP knowledge-base bindings have run independently since v0.6.0 and are unchanged. The retrieval pipeline itself has zero changes — filtering happens at the entrance (listings and pickers), and hybrid search plus citation lineage behave bit-for-bit the same. Document-level permissions are explicitly out of scope: “some documents visible to some people” fits retrieval-time metadata filtering better than pushing access control into the retrieval hot path.