Check access when a user opens a source citation, even if retrieval was permitted earlier. Roles, sharing links, document status, and account context can change between answer generation and source access.
Citation opening is a new resource request
A citation points to supporting evidence but does not grant permanent authority. The preview, link resolver, and source delivery should apply the relevant current policy under the actual system’s supported behaviour.
For a proposed resolver, preserve stable source identity and cited version while resolving trusted user context at opening. Distinguish a missing document, revoked access, expired share, and source-system outage through safe messages.
Do not embed long-lived privileged URLs in generated answers as a shortcut. A link can be copied to another person or remain in a conversation after the original permission changes.
Test a fictional revoked project citation
An employee receives an answer citing a restricted project document. Later, their project membership ends. Opening the old citation should not expose the document through a stale application proxy or cached preview.
A different employee receives the copied link. The resolver must use that viewer’s actual scope rather than the identity of the person who generated the answer. The visible error should not reveal private titles or metadata beyond policy.
| Citation condition | Expected response |
|---|---|
| User still authorised | Open permitted cited source or version |
| Access revoked | Deny protected delivery |
| Different viewer | Evaluate that viewer’s scope |
| Source removed | Explain unavailable evidence safely |
| Source updated | Apply explicit version and freshness behaviour |
Inspect redirect targets, preview endpoints, and media or file storage paths. Protecting only the first click endpoint is insufficient if the final object URL bypasses the intended control.
Preserve evidence limits honestly
A citation may refer to a version no longer retained. Do not silently open a changed page and imply it proves the historical answer. Show the supported version relationship or explain the limit.
Rechecking access adds latency and a dependency on source identity services. Caching can be appropriate only within the defined freshness policy. Test failures and revocation rather than assuming an earlier successful retrieval remains valid indefinitely.
This citation design is proposed. The voice integration case study describes related retrieval work without claiming this resolver. Pair it with shared-link handling.
Citation access FAQ
Does an answer citation grant access to the source?
No. The viewer still needs the relevant current permission.
Can a copied citation use the original employee’s identity?
Not to bypass the new viewer’s scope.
What should a citation test cover?
Check revocation, user changes, redirects, previews, final storage access, version changes, and safe failure messages.