Get client feedback on your Sanity-powered frontend

Q: What does the Presentation Tool display?

It renders the configured frontend inside an iframe in Sanity Studio and connects routes and rendered content to the relevant documents and fields.

Q: Can stakeholders preview drafts without Studio access?

Yes, when shared preview access is enabled. Sanity says it creates a shared secret with no TTL; disabling shared access immediately invalidates that secret.

Q: Does the normal draft-preview secret last forever?

No. Sanity documents expiring per-session preview secrets. The shared preview access secret is the no-TTL exception while shared access remains enabled.

Q: What is the difference between a public dataset and a private dataset?

Anyone can query a public dataset without authorization. A private dataset requires an authenticated user or an authorized personal or robot token.

Q: Do I need to configure CORS for a browser frontend?

Yes when that frontend reads Sanity from a different origin. Sanity requires you to add the website origin to the project’s allowed CORS origins.

Q: Can I put a private dataset token in frontend JavaScript?

Sanity advises against exposing access tokens in public browser bundles. Fetch private data through a controlled server or another appropriately protected implementation.

Q: Does BugSmash change Sanity data or permissions?

No. Studio roles, dataset visibility, preview secrets and frontend authentication remain separate. BugSmash records contextual review on the rendered browser surface.

Paste the separately deployed frontend or an enabled shared-preview URL, send one review link, and collect contextual comments on the rendered experience.

See how it works

Loved by1,250+Agenciesand companies in 100+ countries

Sanity manages structured content. Review happens on the connected frontend.

Sanity Studio, Content Lake and the Presentation Tool support editorial work, while the website or application remains a separately deployed frontend.

Four documented boundaries matter before stakeholder review:

Sanity Studio is an editorial application.
Studio is a browser-based React SPA connected to Sanity APIs and Content Lake. A sanity.studio deployment is not automatically the customer-facing website.
The Presentation Tool embeds a frontend.
It renders the configured frontend in an iframe and can connect that preview to documents and fields in Studio.
Draft mode requires a secure handshake.
The frontend validates the preview secret, sets its draft-mode state and redirects the preview. This is separate from ordinary published-content access.
Dataset visibility controls data reads.
Anyone can query a public dataset, while a private dataset requires an authenticated user or a request carrying an authorized token.

BugSmash keeps external feedback on the rendered experience:

share the accessible frontend or enabled shared preview, retain page context, and leave Studio, dataset and application access under their existing controls.

How it works

Three steps to a reviewed Sanity-powered site

Prepare the frontend

Deploy the website or application frontend and confirm it can load the intended published content or authorized preview state from Sanity.

Choose published or preview review

Use the normal frontend URL for published content, or enable Sanity shared preview access when stakeholders need an authorized draft preview without Studio access.

Send and resolve the review

Paste that browser URL into BugSmash, collect contextual comments, update the content or frontend, and verify the rendered result.

Review the Sanity-powered frontend, not the content workspace

Comment on the deployed frontend

Attach feedback to the rendered website or application rather than a Studio document or Content Lake response.

Review an enabled shared preview

Use Sanity shared preview access when stakeholders without Studio access need to see draft-mode content.

Keep Studio access private

External reviewers can comment on an accessible frontend without becoming Sanity project members.

Check responsive layouts

Review desktop, tablet and mobile presentation and retain the viewport with each comment.

Capture technical context

Keep the page URL, browser, operating system, viewport and screenshot with each website comment.

Review any connected frontend stack

Use the browser URL of the frontend configured to consume Sanity content, independent of where that frontend is hosted.

Which Sanity-related URL should I review?

Use the deployed frontend or a deliberately enabled shared preview. Studio, Presentation Tool, dataset and application access remain distinct.

Your URL	Review by URL	What to do
Public Sanity-powered frontend	Works	Paste the public website or application URL into BugSmash.
Accessible staging frontend	Works	Use the staging URL after confirming the reviewer can open it.
Sanity shared preview URL	Works while enabled	Enable shared preview access and share the resulting stakeholder preview while it remains active.
Presentation Tool inside Studio	Studio access required	Use shared preview access or the deployed frontend for stakeholders who do not have Studio access.
Frontend backed by a private dataset	Implementation-dependent	Review the rendered frontend after its server-side or authenticated data access is configured; never expose a private token in public browser code.
Frontend behind login or access protection	Access-dependent	Authenticate in the review session or use the Feedback Widget. A pasted URL does not bypass frontend authentication.

Using the Feedback Widget on a Sanity-powered frontend

Add the BugSmash Feedback Widget to the deployed frontend when reviewers must stay inside an authenticated, personalized or stateful experience. Install it in the application, not in Content Lake.