Sanity project settings restricted to one admin despite multiple admins

It sounds like you're experiencing a frustrating permissions issue that appeared suddenly. Based on the Sanity documentation on roles and permissions, here are some things to check:

Common Causes for This Issue

1. Single Sign-On (SSO) Role Mapping If your organization recently enabled or updated SSO with role mapping rules, this could explain the overnight change. When SSO role mapping is configured to be the sole source of role assignment, manual role changes are locked. According to the roles documentation, you'll see a popover message stating "roles are handled by identity provider and cannot be manually updated."

2. Organization-Level vs Project-Level Permissions There's an important distinction in Sanity's permission system:

• Organization owners have different permissions than project administrators
• Even if someone is an admin at the project level, certain organization-level settings require organization owner privileges
• According to the platform terminology docs, "All administrator members in a project will have access to project settings," but organization-level controls are separate

3. Presentation Tool Permissions For the Presentation Tool specifically, access requires proper project settings permissions. The documentation notes that members need Project Details set to "read" at minimum, and ideally Project Members also set to "read" for the best Studio experience.

What to Check

1. Navigate to your project at sanity.io/manage and review the Members section
2. Check if SSO role mapping was recently enabled - look for any indicators that roles are managed by an identity provider
3. Verify organization ownership - the person who can change settings might be the organization owner rather than just a project admin
4. Review the Access tab in project settings to see if custom roles were recently modified

Potential Solutions

• If SSO role mapping was enabled, you may need to adjust the mapping rules or disable the "restrict role assignment" option
• Ensure that project administrators have the "Administrator" role (not just "Editor" or "Developer")
• Contact the organization owner to grant necessary permissions
• Check if there were any recent changes to custom roles or content resources that might affect access

Has your organization recently made any changes to authentication methods or added SSO? That would be the most likely culprit for an overnight change like this. If none of these apply, I'd recommend reaching out to Sanity support via their community Slack or email as this could be a bug or platform issue.