External client documents need a trusted client boundary in internal search. Employees serving several clients should not receive cross-client evidence merely because the documents discuss similar products or problems.
Client separation is more than folder naming
Client-scoped retrieval limits evidence according to approved engagement relationships and document permissions. A folder label can support organisation, but it is not sufficient unless the backend enforces the relevant resource policy.
For a proposed model, preserve source system, client namespace, stable resource identity, user relationship, and audience metadata. Keep shared internal guidance separate from client-specific records and define how genuinely reusable knowledge is approved for broader use.
Do not accept a model-generated client identifier as authority. The trusted application should resolve the current context and validate any switch to another permitted client.
Test a fictional two-client query
An employee supporting client A asks about an export issue. Client B’s incident report is highly similar and contains a useful workaround. If the employee lacks B access, that report must not enter the answer context, title suggestions, or source previews.
A separate approved internal article may contain a general remedy derived through the organisation’s publication process. Its availability does not justify copying B’s private details into A’s response.
| Resource relationship | Expected behaviour |
|---|---|
| Current permitted client document | Eligible under source policy |
| Unrelated client record | Excluded before generation |
| Shared approved internal guidance | Available to its defined audience |
| Employee with several client roles | Explicit valid context and scope |
| Client relationship ends | Revocation and derived-copy handling |
Use synthetic client-specific markers and identical question wording under different employees. A leakage test should inspect actual retrieval context, not only whether the final answer mentions the other client’s name.
Keep mapping and exports accountable
Connectors can use different client identifiers, so maintain trusted namespaces and relationships. Exports, debugging samples, and support attachments must preserve the same separation. A copied document does not become internal public knowledge automatically.
Separate indexes can simplify client isolation but increase operational overhead. A shared index can be appropriate with tested enforcement, freshness, and metadata integrity. Evaluate actual guarantees rather than assuming one architecture label establishes safety.
This design is proposed. The voice integration case study describes white-label and integration work without claiming this client-search system. Pair it with cross-system retrieval.
Client search FAQ
Can semantic relevance override client scope?
No. Permission and client relationship govern eligibility before ranking.
Should client examples be reused in general guidance automatically?
Only through the approved review and minimisation process, not by copying private context.
What proves separation?
Test allowed access, cross-client denial, context assembly, metadata, previews, exports, and revocation under realistic fixtures.