# We heavily customized Sanity Studio, does that affect the Croct mapping?

Asked by Lena Hoffmann on 2024-09-18. Tags: sanity, studio, integration.

Before I propose Croct to a client, I want to rule out rework in their Studio.
The setup is heavily customized: a custom desk structure grouping documents by
market, several custom input components for structured fields, and custom
document actions that enforce an approval step before publish.

From the integration description it sounds like the mapping happens between
Sanity components and Croct slots on the frontend side, but I could not find an
explicit statement about whether the integration installs anything into Studio
or hooks into the publish pipeline. Does any of our Studio customization need
to change, or does the integration not touch Studio at all?

## 1 answer

### Answer from joris_v (2024-09-19)

You can rule out the rework. The integration lives entirely on the frontend
side: your existing Sanity components map to Croct slots in your application
code, and nothing gets installed into Studio, no plugins, no schema changes,
no hooks into publish. Your custom desk structure, input components, and the
approval document actions all keep working exactly as they do now.

Authoring does not change either. Content stays in Sanity and serves as the
fallback whenever no experience applies, so editors keep their current
workflow, including your enforced approval step, and Croct only decides which
variant renders for a given visitor.

Also worth mentioning for the client conversation: adoption is gradual and
component-level, with no migration. We started with a single hero component
on one client project, left the rest of the site alone, and expanded one
component at a time as the client asked for more. Studio stayed untouched
throughout.