Production readiness

Check the whole flow before launch.

Run these checks against your own CMS using an ordinary editor account. A working demo confirms the Picker experience; your routes, saved content and publishing flow need their own checks.

01 · Security

Credentials and origins

Live token is stored in the CMS secret manager.No persistent token is present in frontend bundles, HTML, URLs or logs. Only required scopes were requested.Test and live credentials are separate. Every CMS origin is registered exactly.Protocol, hostname and port match the deployed editor. Picker bridge endpoints require editor login and CSRF.Session ownership is checked during redemption.

02 · Persistence

Content model

Artwork fields store provider, type, ID and rendition.Collection fields do not store a rendition. Saved content contains no launch codes or signed URLs.Keep the artwork reference even if you import the image into your local media library. References are resolved when content is reopened or rendered.The selected rendition is passed through unchanged. Publication validates availability when required.Editors receive a useful message for unavailable content.

03 · Delivery

Assets and rights

Signed URLs are requested close to use.Expiry is honoured and URLs are not copied into permanent CMS content. The delivered version_key matches the saved rendition.The physical response variant is never stored as the artwork rendition. Rendering uses the selected version's delivery facts.Width, height and MIME type come from the matching available_versions[].delivery object. Partial asset denial is handled per item.Missing and restricted variants do not break unrelated artwork. Required credit is visible wherever the artwork is displayed.Only declare credit_display: true when the complete attribution flow works.

04 · Operations

Reliability and recovery

Every request is traceable.The CMS records status, problem code and request ID without recording secrets. Retries are bounded and idempotent.Picker redemption reuses a stable key after uncertain responses. Updates and withdrawals reach saved content.The Sync job can resume after a restart. If you use webhooks, test actual delivery and duplicate events. Credential rotation has been rehearsed.A replacement can be deployed before the previous credential is revoked.

Final verification

Run an editor acceptance check.

Select two artworks, save and reopen the entry, then confirm the chosen versions display. Cancel a later selection and check that nothing is lost. Test a network failure, an expired session and an unavailable rendition; each should leave the editor with a clear next step.

Open CMS demo ↗ Review failure handling →