Issue with changes not reflecting in queries after adding an editor member to the project.

I think I've found your issue! This is likely related to a recent change in Sanity's API regarding perspectives.

The Vision tool in Sanity Studio uses the Content Lake API, and there was a breaking change in API version 2025-02-19 where the default perspective changed from raw to published. This is probably what's happening to you.

What's going on with perspectives?

In Sanity, when you edit and save a document, it creates a draft version (with an ID like drafts.my-document-id). When you publish, the draft becomes the published document. Perspectives control which version of documents you see:

• raw - Shows ALL documents (both drafts and published)
• published - Shows ONLY published documents (no drafts)
• previewDrafts - Prioritizes drafts over published when both exist

Why this might have started happening

If your project recently updated to use the newer API version (which could have happened automatically or when the editor was added), Vision might now be using the published perspective by default instead of raw. This means if there's any issue with the publish step, you won't see your changes.

How to troubleshoot

1. Check the perspective in Vision: In the Vision tool, look for a perspective selector (usually in the toolbar or params section). Try explicitly setting the perspective:

   • Add perspective=raw to your Vision query parameters
   • Or try perspective=previewDrafts to see if your draft changes appear

2. Verify the document published correctly: In Studio, check if the document shows as published (no "Publish" button visible, and no draft indicator). Sometimes publish actions can fail silently.

3. Check for draft documents in your query: Try this GROQ query in Vision to see both versions:

   *[_type == "yourDocumentType"] {
     _id,
     _type,
     // your other fields
   }

   If you see both drafts.document-id and document-id, the draft might not have published properly.

4. Try re-publishing: Sometimes clicking "Publish" again can resolve stuck draft states.

The timing with adding an editor member is likely coincidental, unless that action triggered some project configuration changes or an automatic update to a newer API version. The editor role itself shouldn't affect how documents publish or how queries work.

Quick fix: Try adding perspective=raw to your Vision query parameters and see if your changes show up. If they do, that confirms the perspective change is the issue!