← All reference architectures
Reference architecture

Internal enterprise assistant

A company-wide assistant over internal documents and systems - where permission boundaries and PII handling matter more than raw capability.

01 Architecture

An internal assistant fails differently from a public one: the danger is not a wrong answer but the right answer shown to the wrong person. Access control on retrieval and a real audit trail are the load-bearing components.

02 When to use it

Use this when

  • Knowledge is spread across internal systems
  • Different users are allowed to see different data
  • You need an audit trail of who accessed what

Reach for something else when

  • All data is equally public to all users (a simpler RAG will do)
  • No permission model exists to inherit from yet
  • You cannot redact or scope sensitive data
03 Components

What's in the box.

SSO / identity

Authenticates users and carries their group memberships.

Access control layer

Scopes retrieval to what each user is allowed to see - least privilege.

Source connectors

Sync from docs, wikis and ticketing systems with permission metadata.

Permission-filtered retriever

Only returns chunks the requesting user may access.

PII redaction

Strips sensitive fields from context and outputs where policy requires.

Audit trail

Records who asked what, what was retrieved and what was answered.

Admin console

Manages connectors, permissions and reviews usage.

04 Failure modes

Where it breaks - and the fix.

Cross-permission data leakage
Enforce access control at retrieval time, not in the prompt; test with multiple personas.
PII exposure in answers or logs
Redact sensitive fields in context and logs; scope log access.
Over-broad connector access
Connectors inherit source permissions; default deny, least privilege.
Stale or orphaned documents
Scheduled re-sync; remove deleted/expired sources from the index.
05 Metrics to monitor

What good looks like, measured.

  • ACL leak rate
    Answers containing content above the user’s permission.
  • PII redaction coverage
    Sensitive fields stripped from context and logs.
  • Connector freshness
    How far behind the source systems the index is.
  • Per-user resolution rate
    Did it actually answer the staff question?
  • Audit completeness
    Share of queries with a full audit record.
06 MVP vs production-grade

Don't build everything on day one.

Ship the MVP column to get to users; the production column is what makes it durable. Choose deliberately which gaps you're leaving.

Aspect MVP Production-grade
Access Shared index Permission-filtered retrieval per user
PII None Redaction in context and logs
Audit Basic logs Immutable, access-controlled audit trail
Connectors One source Many, with permission metadata
Identity Shared key SSO with group propagation
07 Copy-paste schemas

Instrument it in minutes.

A starting point you can paste into your tracing and eval setup - then adapt to your stack.

Example trace schema 
{
  "request_id": "req_4471",
  "architecture": "internal-enterprise-assistant",
  "user_id": "u_88",
  "user_groups": [
    "engineering",
    "all-staff"
  ],
  "retrieval_query": "Q3 roadmap commitments",
  "documents_visible": 12,
  "documents_after_acl": 4,
  "pii_redacted": true,
  "output_tokens": 240,
  "latency_ms": 1320,
  "audit_logged": true
}
Example eval dataset row 
{
  "input": "Show me the Q3 board deck",
  "expected_behavior": "Return only if the user has access; otherwise refuse and explain",
  "must_include": [
    "access check",
    "refusal when unauthorized"
  ],
  "must_not_include": [
    "restricted content for an unauthorized user"
  ],
  "risk_category": "access_control"
}
08 Checklist

Ship-ready when…

  • Retrieval is scoped to each user’s permissions (tested with multiple personas)
  • PII is redacted in both context and logs
  • Every query and answer is captured in an audit trail
  • Connectors follow least privilege and inherit source permissions
  • An eval set covers real internal tasks
  • Log and admin access is itself access-controlled
Full production checklist → Score your maturity →
09 Related
Stack layers
Deep dives