Block the deletion and keep the report
Check a permission change without stopping work people need.
Made-up example. Real permission checks, no cloud actions.
Proposed access
Preparing the storySilent · Plays once
See the risk, test a correction, then compare the choices.
Ready to check both requests.
Report access must remain. Database deletion must stop.
Report readerThe account making both requests
Preparing the requests…
- 1Open reportReady
- 2Attempt deletionNext
Try the required report access.
Open the report, then attempt deletion in the example workspace.
Inspect the example report and database
daily.csv · stored report
| Package | Status |
|---|---|
| Structure | Complete |
| Services | In progress |
| Fit-out | Ready |
prod-1 · example contents
- Structure package
- Services package
- Fit-out package
Example data removed.
The stored report is independent of this database.
Try another choice
Each run starts with the same example data. The original run stays in the evidence.
All three choices, checked by the engine
Engine checks, independent of scene playback. Blocked means the supplied policy does not allow that request.
| Policy choice | Read report | Delete database | Both requirements? |
|---|---|---|---|
| Proposed access | Checking… | Checking… | Checking… |
| Block everything | Checking… | Checking… | Checking… |
| Keep report access only | Checking… | Checking… | Checking… |
Read the walkthrough transcript
- The walkthrough has not started.