Sanity
A Sanity project, dataset, compatible document schema, and write-capable robot token
Ownership and availability
You own the Sanity project, dataset, schema, and robot token. Obelo encrypts the token and never returns it to the browser.
Start in Settings → Integrations and check the provider’s current status. This guide describes the configured setup path, not a guarantee of production enablement. Provider approval, plan access and resource permissions still apply.
CMS publishing requires an active Starter Pro plan or higher.
Before you connect
- Developer or administrator access to the Sanity project
- A dataset and document type for the content Obelo will publish
- A dedicated project robot token with Editor-equivalent write access
Connect an existing account
- Open the provider in Settings → Integrations for the intended website.
- Open the project in Sanity Manage and confirm the dataset and schema
- Create a dedicated project robot token in Settings → API → Tokens
- Submit the public site URL, project ID, dataset, and token for validation
If you need a new resource
- Create a Sanity project and dataset
- Deploy a Studio schema for articles or the intended content type
- Create a dedicated write-capable project robot token for Obelo
Permissions to check
- Use a project robot token instead of a personal token
- The token must create and update documents in the selected dataset
Verify and troubleshoot
Return with the public URL, project ID, dataset name, and robot token.
No compatible Sanity dataset or content target was verified. Check the project ID, dataset, schema, and token role.
Confirm the selected account or resource and inspect the verification or sync result. A saved connection is not proof that an import or publication has completed. Test the intended workflow with an appropriately reviewed item.
Disconnect or change access
Use the provider’s management controls in Obelo to disconnect when supported. Revoke the grant or rotate a dedicated credential at the provider if access must end immediately. Review already-imported data separately; disconnection does not remove content already published elsewhere.
Something unclear or out of date?
Suggest a correction