Skip to content

Platform

Manage users

Tested with:Databasezy API v1 · supabase-js 2

Platform services → Auth → Users lists the project’s users with how they signed in (email, phone, providers, SSO, anonymous) and when they last did.

  • Find: search by email, name, phone or id; filter confirmed, unconfirmed, anonymous or banned; sort by sign-up, last sign-in or email; 25, 50 or 100 per page.
  • Add: create a user with a password (optionally already confirmed) or send an invitation email.
  • Act on a user: send a password reset, ban for a duration (their next token refresh fails with user_banned) and unban, sign out all sessions, unlink an identity, see sessions and factors, and delete (soft delete keeps the row anonymised; hard delete removes it).

Every change is written to your organization’s audit log with who made it. Owners, admins and developers can change users; read-only members can only look.

The same actions are on the management API, scoped to your organization and project:

MethodPath (under /v1/orgs/{org}/projects/{project}/auth/users)
GET?q=&filter=&sort=&page=&per_page=
POST/ (email or phone, password, email_confirm, metadata), /invite
GET / PUT / DELETE/{user_id} (?soft=true to soft-delete)
POST/{user_id}/recover, /{user_id}/logout
GET/{user_id}/sessions
DELETE/{user_id}/identities/{identity_id}

From your own backend you can also use Supabase’s admin API on the project endpoint with a secret key: supabase.auth.admin.listUsers(), createUser, updateUserById, inviteUserByEmail, generateLink, deleteUser and mfa.listFactors / deleteFactor. The publishable key is refused there.

zb migrate supabase moves a Supabase project’s users with their ids, identities and password hashes (bcrypt), so they sign in with their old passwords and your foreign keys to auth.users keep working. The import endpoint takes the secret key only; see Move from Supabase for the whole move.