# After adding Croct to our Sanity site, who edits what where?

Asked by Berit Halvorsen on 2025-01-22. Tags: sanity, workflow, onboarding.

Hi all! Our editors know Sanity Studio inside out, and they just received
Croct access so they can work with experiences. Before the questions start
flooding my inbox, I would love the clean mental model to share with them:
which edits belong in Studio, which belong in the experience editor, and how
do previews differ between the two? Thank you in advance

## 1 answer

### Answer from Tessa Bright (2025-01-22)

The mental model that stuck with our team is default vs everything else.

Studio owns the default. Whatever a visitor sees when no experience applies
to them lives in Sanity and gets edited exactly as before. Nothing about
that workflow changes, which is why your editors will feel at home.

The experience editor owns the deviations. Variant copy for A/B tests and
audience-specific content are edited there, and that is also where
experiences and experiments get published, paused, and where winners are
rolled out. All of that happens without code changes, so editors do not need
a developer in the loop for day-to-day experiment work.

Previews follow the same split. Studio previews keep showing the default
document, same as today. For variants, the experience or experiment editor
generates preview links that are shareable and valid for 24 hours, which is
what you send a stakeholder who wants to see what a specific audience or
variant looks like.

One-line version for your guide: "If everyone should see it, edit it in
Studio. If only some people should see it, edit it in Croct."

#### Reply from Berit Halvorsen (2025-01-23)

The one-line version is going straight into our onboarding doc. Thank
you, this is exactly the clarity I needed!