How to give editor access to Sanity CMS for portfolio changes?

3 replies
Last updated: Jul 7, 2023
I built a portfolio, it's up and running and I'm happy with it. Now, i want to be able to allow someone else access to the CMS to edit, change/upload images, etc. I've sent the invite, his role is "editor", he accepted, but we don't see how/where he can make edits/changes. help? I'm a newbie, so be gentle?
AI Update

Good news - this is a common issue with a simple solution! Your editor has accepted the invite and has the right role, but they need to know where to go to access the Studio.

When you deployed your portfolio, you (or your hosting setup) created a Sanity Studio - that's the content management interface where editing happens. Your editor needs the Studio URL to make changes.

Find your Studio URL:

If you deployed using the sanity deploy command, your Studio is hosted at a URL like:

https://your-project-name.sanity.studio

You can find this URL by:

  1. Running sanity manage in your project folder (opens your project settings in browser)
  2. Looking in your project's API settings in the Sanity management console
  3. Checking the output from when you first ran sanity deploy

Alternative locations:

  • If you're self-hosting or using Vercel/Netlify, your Studio might be at a custom URL like yoursite.com/studio or a separate domain
  • If you embedded the Studio in your Next.js app (or similar framework), it's typically at a /studio route

Share the Studio URL with your editor:

Once you find it, simply send them that URL. When they visit it and log in with their Sanity account (the one that accepted your invite), they'll see the Studio interface where they can:

  • Edit content
  • Upload and manage images
  • Create new posts/pages
  • Make any changes you've configured in your schema

Pro tip: The default "Editor" role should allow creating, editing, and publishing content, which sounds perfect for your use case!

If they still can't see content or make edits after logging in, you might need to check if there are any custom roles configured or ensure your Studio is pointing to the correct dataset.

Show original thread
3 replies
Hi
user F
! You’ve been working on creating what’s known as the Sanity Studio, which has code that includes schemas and potentially things like components. Most likely, you’ve worked on that on your local system, which operates in development at localhost:3333 by default. Your editor will need to access that Studio as well, but wouldn’t access it via your computer, so there are two options:
1. If your colleague is also a developer, one approach is to share the codebase (e.g., via GitHub), which they can clone and run locally as well. However, this is not ideal for someone operating as an editor, which brings us to
2. You can deploy your Studio so it’s globally accessible (“globally” here means from anywhere, but the user must still be authenticated). The Studio can be hosted anywhere (e.g., Vercel, Netlify, Geocities, or your own hosting service), but we also offer Studio hosting (no cost) to which you can deploy the Studio. From your terminal, you can run
sanity deploy
. You’ll be prompted to select a hostname, which must be unique. After that, the Studio is accessible at
https://<hostname>.sanity.studio
. Your editor can log in there. Any time you make changes to your schemas that you want to make available to your editor, you can run
sanity deploy
again and the Studio will be built and deployed.We recommend keeping your Studio codebase version controlled and/or backed up, as if you were to lose the Studio codebase it cannot be inferred from the deployed copy.
thanks sooo much. I JUST got the studio up and running. it was fast and easy.
Great to hear!

Sanity – Build the way you think, not the way your CMS thinks

Sanity is the developer-first content operating system that gives you complete control. Schema-as-code, GROQ queries, and real-time APIs mean no more workarounds or waiting for deployments. Free to start, scale as you grow.

Was this answer helpful?