Issue with logging in to a project and getting internal 500 error, which was resolved.

I'm sorry you're running into this frustrating issue! A 500 internal server error when trying to access a specific project (while other projects work fine) is definitely unusual and points to something specific with that project's configuration or your access setup.

Here are the most likely causes and what you can try:

1. Project-level permission issue Sometimes there can be a misconfiguration in how your user account was invited or assigned permissions to the specific project. Since you can access other projects fine, your Sanity account itself is working correctly - this is isolated to this one project.

2. Organization-level access conflict If the project is under a different organization than your other projects, there might be an organization-level permission issue. Projects can be moved between organizations, and sometimes access settings don't sync properly during or after such moves.

3. What you should do:

Since this is a server-side error (500 status), there's likely something in the project configuration that needs to be fixed by someone with admin access:

• Contact the project admin/owner who invited you and ask them to:

  • Remove you from the project completely in Sanity Manage
  • Re-invite you with fresh permissions
  • Check if there are any custom access control rules that might be causing issues

• Reach out to Sanity support directly at support@sanity.io or through the in-app chat in manage.sanity.io. Since this is a 500 error (server-side issue), it's likely something they'll need to investigate in their logs. Include:

  • Your email address
  • The project ID you're trying to access
  • The exact error message/screenshot if possible
  • When the issue started

The fact that you've already tried different browsers and private browsing (good troubleshooting!) confirms this isn't a local cache or cookie issue - it's something on Sanity's end that needs admin or support intervention.