AI for business · 03

Internal-Document Chatbots: Test Access Permissions Before Launch

An acceptance checklist for RAG chatbots covering roles, revoked documents and citations, with evidence a business owner can review.

An internal chatbot acceptance matrix with test roles, documents, expected outcomes and not-yet-run status.
Friday Works / Journal03 · 2026
ContentsTap to jump to a section
  1. 01Accuracy does not establish authorization
  2. 02Prepare a permission matrix
  3. 03Enforce access during retrieval
  4. 04Retest after changes
  5. 05Check citations and handover
Summary
The one-minute brief
  • Retrieve only documents the current user may read.
  • Retest role changes, revocation and document updates.
  • Citations must preserve the same access boundary.
01

Accuracy does not establish authorization

An internal chatbot can produce a correct answer from a document its user may not read. Acceptance therefore needs access tests as well as answer-quality tests.

Retrieval-augmented generation supplies relevant documents to a model. This guide focuses specifically on the permission boundary rather than repeating an introductory RAG explanation.

02

Prepare a permission matrix

Friday Works recommends test roles such as sales, accounting and content administration, with shared, restricted and revoked documents. Specify allowed and denied outcomes before testing.

Include direct questions and paraphrases against designated test data. A restricted payroll document must not become available merely because a user asks for a summary.

03

Enforce access during retrieval

OWASP recommends validating permissions on every request and denying by default. Retrieval tools should use the current user identity. A natural-language instruction is not a substitute for system authorization.

Record the test account, retrieved document and applicable policy without collecting unnecessary sensitive content in logs.

04

Retest after changes

Revoke access in a test environment, start a fresh query and check the answer and source link. Repeat for deleted or newly restricted documents.

Explain cache expiration or invalidation and verify the agreed revocation delay. Testing with an administrator is not evidence of employee isolation.

05

Check citations and handover

A blocked answer with an accessible download is still a failed boundary. Test file names, excerpts, downloads, suggestions and shared history using the restricted role.

Record evidence, exceptions and ownership. Answer quality and access control are independent acceptance criteria.

References

Sources used in this guide

We prioritise official guidance and primary technical sources. Visit each source for full context and the latest updates.

  1. Authorization Cheat SheetOWASP
  2. Top 10 for Large Language Model ApplicationsOWASP
  3. Original acceptance worksheet, 16 October 2026; screenshot of an authored document, not a completed testFriday Works

Written and reviewed by

Friday Works technology team

A perspective shaped by designing websites, building software, automating operations, integrating AI and assessing security for businesses.

Content is reviewed to reflect methods that can be applied in practice. We update it when the process, technology or underlying evidence changes materially.

About Friday Works