imbahub
Menu +
US
Talk to us
IMBAHUB / Knowledge & guides

Test who can fetch a draft after preview access changes.

A working preview button establishes only the normal route. Exercise anonymous requests, old sessions and revoked links or keys under the chosen design. Use synthetic drafts in an authorized test environment. Real secrets are unnecessary as test content.

Four access states to keep distinct
  1. Authorized

    Right draft from the right source.

  2. Anonymous

    No unauthorized delivery.

  3. Revoked

    Old route follows the agreed block.

  4. Public

    Only intended published evidence.

Test delivery after permission changes, rather than only the editor's button.

The preview button is gone but an old link shows the draft. What is missing?

Evidence that revocation affects delivery. Compare against the agreed model and resolve the difference before acceptance.

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.

ExerciseExpected under the chosen modelEvidence
Intended editorPermitted identified versionRight record, language and environment
Anonymous requestNo unauthorized draft deliveryActual response without private content
Expired or revoked linkAgreed lifetime and blocking applyFresh request with the old link
Existing open sessionPermission change has intended effectRefresh and new resource requests
Public page routeOnly intended public contentNo 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.

Sources and further reading

Questions, answered

Are a preview key and editor role one permission?

Not necessarily. Map source access and preview-web access, then test them separately.

Does a preview error prove drafts are protected?

Not alone. Use a working positive control and inspect direct access and public delivery too.

IMBAHUB

Let’s plan your website

Test one synthetic draft before and after revocation and through its public counterpart.

Talk to us
Existing English product interface with fictional demonstration content; reused for the US website.

Existing English product interface with fictional demonstration content; reused for the US website.