Write the access model and lifetime first
Identify what grants access: editor session, sharing link, server key or a combination. State who may see each environment and how that right ends. A CMS token and a person's access to the preview website are not necessarily the same control.
Create a synthetic draft with separate markers for each language and environment. Record the expected version. A positive control must show the intended editor can view it; otherwise an API failure could be mistaken for successful access restriction.
Exercise old routes after revocation
Open the view with an allowed test role and retain its session. Revoke permission through the agreed administration and make a fresh request. Try a previously created sharing link where applicable.
Where a separate preview credential is used, the owner should test rotation or withdrawal through the test chain. Record which stage stops and any agreed delay. A disappearing button does not establish that an old address is denied.
| Exercise | Expected under the chosen model | Evidence |
|---|---|---|
| Intended editor | Permitted identified version | Right record, language and environment |
| Anonymous request | No unauthorized draft delivery | Actual response without private content |
| Expired or revoked link | Agreed lifetime and blocking apply | Fresh request with the old link |
| Existing open session | Permission change has intended effect | Refresh and new resource requests |
| Public page route | Only intended public content | No synthetic draft marker |
Compare preview with public routes and resources
Open the public counterpart without an editor session. Compare markers, language and related files. Check that caching does not deliver a draft from an earlier authorized preview to another visitor.
Exercise wrong environment and language identifiers within the authorized sample. An unlabelled source switch can make editors review the wrong page. Fallback needs to be intentional and visible, rather than hiding a missing draft.
Report revocation without promises about downloaded copies
Inspect client code, generated public files and inappropriate logs for secret exposure. Do not print real credential values in the report. Describe how errors and expired access are explained to editors.
Record environment, record version, roles, timing, revocation and observations. Restricting future access does not erase copies already downloaded. This is a focused access and delivery exercise, rather than complete security certification.