Can't log into Studio URL despite being logged into sanity.io/manage

I can see you're able to log into www.sanity.io/manage but having trouble accessing your Studio. Let me help you troubleshoot this.

First, verify your CORS settings

The most common cause of Studio login issues is missing or incorrect CORS (Cross-Origin Resource Sharing) configuration. Here's how to check:

1. Go to manage.sanity.io (where you're already logged in)
2. Select your project
3. Navigate to Settings → API → CORS Origins
4. Make sure your Studio URL is listed there (e.g., https://your-project.sanity.studio or your custom domain)
5. Important: Check the "Allow credentials" checkbox for that origin

Without proper CORS configuration, your Studio won't be able to authenticate you even though you're logged into Sanity's main platform. The "Allow credentials" setting is particularly crucial for authentication to work properly.

Why password reset doesn't help

Password reset won't solve this issue because you're already successfully logged into manage.sanity.io. This isn't a password problem—it's about your Studio being unable to verify your existing authentication.

Other things to check

Clear your browser cache and cookies for both sanity.io and your Studio domain. Sometimes stale authentication data can cause login loops.

Try a different browser or incognito/private mode to rule out browser extensions or cached data interfering with authentication.

Verify your Studio URL is correct. If you're using Sanity's hosted Studio (deployed with sanity deploy), it should be at https://your-project-name.sanity.studio. You can find the correct URL in your project settings at manage.sanity.io.

Check if your Studio is deployed. If you're trying to access a locally running Studio at localhost:3333, make sure you've actually started it with npm run dev or sanity dev in your project directory.

Managing your account

If you need to manage login methods or account settings (like adding email/password authentication alongside GitHub or Google), you can do that at accounts.sanity.io, but again, this won't resolve the Studio access issue if CORS is the problem.

The CORS configuration is the first thing to check—it's the most frequent cause of this exact scenario where manage.sanity.io works but Studio access fails.