Contribution · Application — HR

AI for Internal Knowledge Search Assistants

In a 5,000-person company, the answer to every question already exists somewhere — a Confluence page, a Slack thread, a Notion doc, an email. Enterprise search is notoriously bad. LLMs with permission-aware retrieval across all those corpora can actually answer the question, with citations. The risks are permission bleed (showing someone data they shouldn't see) and knowledge becoming stale as docs age.

Application facts

Domain
HR
Subdomain
Knowledge management
Example stack
Claude Sonnet 4.7 for retrieval-augmented responses · Glean / Microsoft Copilot / Danswer as the platform · pgvector or Elasticsearch with permission-aware retrieval · Connectors: Confluence, Notion, Slack, Google Drive, SharePoint · Admin dashboard for usage + data governance

Data & infrastructure needs

  • Source systems with permission metadata
  • Employee identity and group membership
  • Content freshness signals
  • Audit log infrastructure

Risks & considerations

  • Permission bleed — users seeing data they shouldn't
  • Stale content — confidently wrong answers from old docs
  • Data sovereignty — cloud LLMs processing internal IP
  • Over-consolidation replacing human knowledge-sharing culture
  • Employee surveillance if query logs are abused

Frequently asked questions

Is enterprise internal search safe?

Only with permission-aware retrieval — every user's view respects source system ACLs. Test with dummy accounts at all privilege levels before rollout. Limit query log retention and access to prevent misuse.

What LLM is best?

Claude Sonnet 4.7 or GPT-5 for response generation. The bigger decision is the platform — Glean, Microsoft Copilot, Danswer, or in-house — and how it handles permissions. Permission correctness beats answer quality.

Regulatory concerns?

India: DPDPA for employee data, IT policies under labor codes. EU: GDPR + Works Council consultation for employee monitoring. US: NLRB / state privacy laws, SOX for regulated records. Retention of query logs — shorter is safer.

Sources

  1. DPDPA 2023 — accessed 2026-04-20
  2. NIST SP 800-53 — Access Control — accessed 2026-04-20