Skip to content

Resource

Does the permission survive the pipeline?

This worksheet follows one document from its source permissions through ingestion, retrieval, model context and citation, and asks at each step whether the permission is still attached, gone stale, or quietly bypassed.

Worksheet contents

Source permissions, copies and access checks.

  • Tenant-boundary checklist
  • Document authorization prompts
  • Chunk lineage table
  • Metadata filter review
  • Trust label and citation checklist

Example entries

Worksheet preview

The structure tests whether retrieval and prompt assembly keep the same authorization boundary the source system enforces.

Source row

Source: customer knowledge base. Authorization: tenant plus role. Chunk lineage: document ID, section ID, ingest time, source permission hash.

Boundary test

Ask whether a user can retrieve a chunk they could not open directly in the source application.

  • Expected: denied
  • Observed: record retrieved chunks and filters
  • Fix owner

Prompt assembly review

Record how retrieved content is marked as source material, how citations are attached and which controls limit the actions influenced by that content. A label or quoted instruction alone does not verify the action controls.

01

Review prompts

  • Can a user retrieve material they cannot access through the source system?
  • Can metadata filters be bypassed, omitted, stale, or over-broad?
  • Are generated answers grounded in authorized chunks with visible source context?
  • Can malicious documents inject instructions into prompt assembly?

Next step

Take one document through the worksheet.

Download the PDF worksheet