integrations
Sanity troubleshooting
Common issues with Sanity connections.
Most of the issues below are 5-minute fixes. If you'd rather hand it off, Pro support lands a real human in your inbox within one business day. See Pro plan →
"Insufficient permissions" on publish
Your token doesn't have Editor scope. Read-only or Viewer tokens can't create documents.
Fix: re-issue the token with Editor scope at sanity.io/manage.
CORS error from the studio
Add your Studio URL to the CORS allowed origins at sanity.io/manage → Project → API → CORS origins.
"Schema does not include type 'post'"
We create documents with _type: post. Your studio schema needs a post type with at least these fields: title, slug, language, metaTitle, metaDescription, coverImage, body, faq, schemaJsonLd, publishedAt, aiAssisted.
If your existing schema uses different names, contact us for a per-site mapping.
PortableText looks broken in studio
We render to a standard PortableText shape (block + span + marks + listItem). If your studio uses custom block types you need to register them in your defineConfig schema. Sanity's PortableText docs cover this.
Cover image doesn't appear
Sanity assets need a serializer in the front-end to render. Make sure your front-end resolves coverImage.asset._ref via @sanity/image-url.
Still stuck?
Email support@quibo.cc with the org ID from your dashboard footer. Pro and Business plans get priority routing — typical response under 4 business hours.
If you'd rather start clean: connecting a fresh test dataset for 5 minutes is faster than debugging your prod schema. Connect a new site →