In the final round of the access challenge, an assistant has already drafted an update from a study’s recruitment figures. You can delete the draft, revoke future access, or leave access open. If you revoke, the next request changes, and the receipt still shows the earlier disclosure.
That remaining line is the most important part of the example. If it disappeared too, the interface could suggest that the assistant had never received the information.
Walk through the two moments
- Before revocation: an earlier request already included “24 of 40 places are filled,” and a scripted draft was made from it.
- After revocation: no recruitment records are supplied to the next request. The earlier disclosure and the draft remain.
In a real workflow, stopping future retrieval would not establish that a receiving tool had deleted information already supplied to it.
What the control should say
A button labelled “Revoke access” needs to identify the tool and the records it affects. It should explain what stops now and what, if anything, happens to earlier copies. Any promise about deletion would need evidence from the receiving system.
This is why the example keeps the earlier disclosure visible: it separates a change to future access from a claim about past sharing.