Skip to main content

​
Overview

Super admins can manage all users on the instance from /admin/users. The page groups users by family and lets you change roles, move users between families, set passwords for local-login users, and permanently delete accounts.

​
Accessing user management

Navigate to the user management page in your admin dashboard:
You must have the super_admin role to access this page.

​
User list

Users are grouped by family and sorted by activity (most active families first). Each user row shows:

​
Filtering

  • Filter by role: Show only users with a specific role (guest, member, admin, super_admin)
  • Filter by trial status: Show users with expiring-soon or active trials

​
Managing users

All per-user actions are in the actions popover next to each row. Open it to see the options available for that user.

​
Changing a user’s role

Select the desired role from the popover and save. Available roles are guest, member, admin, and super_admin.
You cannot demote the last remaining active super admin. Sure blocks this to prevent losing access to the admin panel.

​
Moving a user to a different family

Super admins can transfer a user to an existing family or create a new one. To move to an existing family, select it from the family dropdown in the popover and save. To create a new family, type the new family name in the name field. A new family is created and the user is transferred atomically.
You cannot change a user’s family and set their password in the same submission. Submit one change at a time.

​
Setting a password for local users

For users who authenticate with a local password, super admins can set a new password from the actions popover. The password must meet all registration criteria:
  • At least 8 characters
  • At least one uppercase and one lowercase letter
  • At least one digit
  • At least one special character (!@#$%^&*(),.?":{}|<>)
Password changes are silently ignored for SSO-only users — they must authenticate through their identity provider.

​
Deleting a family

Empty families (no members) can be deleted from the admin user list. Families with active users cannot be deleted.

​
Deleting users

Super admins can permanently delete a user from the instance. What happens when a user is deleted:
  • The user’s account and all associated data are permanently removed
  • Any active sessions are ended immediately
  • Active OAuth tokens and API keys are revoked
  • An SSO audit log entry records who deleted the account and when
  • The action cannot be undone
Safety checks:
  • You cannot delete your own account. The Delete User action is hidden on your own row.
  • You cannot delete the last active super admin — promote another user first.
To delete a user:
1

Go to /admin/users

Navigate to the admin user list.
2

Open the actions popover

Click the actions menu next to the user you want to delete.
3

Click Delete User

A confirmation dialog opens.
4

Type the user's email to confirm

Enter the user’s exact email address and submit.
Deleting a user is permanent. All of their data is removed and cannot be recovered.

​
Troubleshooting user issues

​
User can’t log in

  1. Check the user’s auth type pill — if it shows only SSO and their provider is misconfigured, they won’t be able to log in
  2. Verify the SSO provider is enabled and configured correctly under /admin/sso_providers
  3. If they have a local password, you can reset it from the actions popover
  4. Review audit logs for specific error messages

​
User is locked out after disconnecting their SSO provider

Sure blocks users from disconnecting their last SSO provider when they have no local password set, and shows a warning on the security settings page. If a user somehow loses access:
  1. Set a local password for them from the admin actions popover (see “Setting a password for local users” above)
  2. Once a password is set, they can log in with email and password and reconnect their SSO provider from /settings/security

​
User has the wrong role

Open the actions popover for the user and update their role. Note that super admin role changes are logged for auditing.

​
Duplicate accounts

  1. Identify the primary account to keep
  2. Delete the duplicate account from the actions popover (requires email confirmation)
  3. Update the user’s email in the identity provider if needed

​
Best practices

Delete user accounts promptly when someone leaves. This revokes all sessions, API keys, and OAuth tokens immediately.
Always have at least two super admins on the instance. Sure prevents you from deleting or demoting the last one, but having a backup avoids getting into that state.
Use the admin password-set feature when a local user is locked out and cannot receive a reset email. Prefer the self-service reset flow when email is available.

​
Next steps

Audit logging

Monitor user authentication and account changes

Admin UI

Manage SSO providers and configuration

OIDC setup

Configure OIDC authentication providers