Don’t Let the Only Admin Lock Themselves Out

I just ran into a scary situation: I’m our account’s only Superadmin, and while testing roles I changed my own role… and instantly lost admin access. With no other Superadmins on the account, I couldn’t switch it back. That meant I was locked out of critical settings and had to ask support to restore access.

Why this matters to us:

• If the sole Superadmin downgrades their own role (even by accident), the whole system becomes unmanageable.

• It can halt work while we wait for a manual fix.

• It undermines confidence that roles/permissions are safely designed.

A simple example:

• We’re onboarding a new workspace.

• There’s only one user (me) with Superadmin access.

• I go to Users → Roles to test permissions and change my role to “Manager.”

• Result: I lose access to Users/Settings and can’t revert. We’re stuck.

What we’d like the product to do:

• Prevent lockout when there’s only one Superadmin in the account (e.g., block self-downgrade until a second Superadmin exists).

• Add a non-editable “Owner” role (or similar) that can’t be removed or downgraded.

• Show a clear warning/safeguard when changing roles that would leave the account with zero Superadmins.

• If you’re already working on customizable roles/permissions, please include these protections by default.

In short: please add built-in safeguards so the only Superadmin can’t accidentally remove their own admin rights.