Search and filter do not cross tenant boundaries

Search endpoints are frequently overlooked during tenant-isolation reviews because they feel like read-only features. But a full-text search that runs across a shared index returns matching documents from every tenant that contains the search term — exposing business names, customer data, proprietary content, and internal notes to anyone who knows what to search for. CWE-285 and OWASP A01 apply; Algolia and Elasticsearch indices that lack per-tenant filters are particularly dangerous because the search engine optimizes for broad recall.

For Algolia, generate tenant-scoped secured API keys server-side so the filter is baked into the key and cannot be removed by the client:

const securedKey = algoliasearch.generateSecuredApiKey(
  process.env.ALGOLIA_SEARCH_KEY,
  { filters: `organizationId:${session.user.organizationId}`, validUntil: Math.floor(Date.now() / 1000) + 3600 }
)

For Typesense, use scoped API keys with a filter condition that locks the key to the tenant's records. For database full-text search (ILIKE, tsvector), always AND organizationId = $1 alongside the search predicate in src/app/api/search/route.ts. Autocomplete endpoints need the same treatment — they are search endpoints too.