How would you design an internal knowledge assistant that respects changing permissions?

Instruction: Explain the access-control flow and the failure behavior, then describe how you would test the design with the client security team.

Context:

A fictional company wants an assistant over general policies, confidential acquisition plans, and employee-specific HR records. Employees already authenticate through company identity. Source systems own document permissions, and permissions can be revoked immediately. The search index updates every hour. Shared caches are proposed to reduce cost. A response may combine several documents.

Updated

Official answer available

Read the opening below, then unlock the full answer and practical guidance.

I would treat the source permissions as an enforced boundary throughout the workflow. The application would authenticate the employee and retrieve only content they are currently authorized to access. It would not accept a user-supplied group name as proof of access or rely on the model to decide who may read a document. Hourly indexing cannot meet immediate revocation by itself...

Upgrade to view official answer

Related Questions