Appearance
Managing users
Users are one of, if not the most critical parts of your application, and it is key to have a solid understanding of how to view and manage them.
Visually managing users
To visually manage your users, go to Data & API → Authentication → Users.
From here, you will have a view of all the users who have been created:
Editing users
If you wish to edit the information of a user, you can simply double-click into a cell and update the information accordingly:
Adding users
If you wish to add a user, you can press the + Insert button in the top left and fill in the information of the new user:
WHY ADD USERS MANUALLY?
Adding users manually is useful for:
- Testing — Create test accounts with specific roles or data
- Admin setup — Add administrator accounts before launch
- Support — Create accounts for customers who need help signing up
Deleting users
If you wish to delete a user(s), you can select the user(s) in the table, and then press the Delete button in the top left:
DELETING USERS IS PERMANENT
Deleted users cannot be recovered. Their authentication data, roles, and session information will be permanently removed. However, data in your tables that references their user ID will remain unless you explicitly delete it.
Managing user fields
The users table includes these fields:
- Email — The user's email address (required for email-based authentication)
- Display name — The name shown in the interface (optional)
- Image — Profile image URL (optional)
- Roles — Roles assigned to this user (see Managing roles)
- Providers — Which sign-in methods the user has used (for example
email,google,github) - User ID — Unique identifier for the user (auto-generated, read-only)
You can copy a user's ID by clicking on the row and using the copy action. This is useful for filters and relationships (for example, filtering records by user_id to show only data owned by that user).
Allowing users to sign up and log in
Having users sign up or log in on their own happens from inside the Interface by using the dedicated authentication actions in workflows. These actions let you build custom sign-up and login forms that fit your app's design.
Available authentication actions
All authentication actions are found in Interface → Workflows → Authentication:
- Sign up with email — Register new users with email and password
- Sign in with email — Authenticate existing users
- Sign in with social provider — Sign in with Google, Facebook, GitHub, etc.
- Request magic link — Passwordless authentication via email link
- Request code — Send OTP code for passwordless authentication
- Sign out — End user session
For a complete list and detailed documentation of each action, see the Email/password authentication provider.
Changing a user's password
As an admin (manually)
You can reset a user's password directly from the Users tab:
- Select the user in the table
- Look for the password reset or edit option
- Enter a new password (minimum 6 characters)
- Save the changes
PASSWORD SECURITY
For security reasons, you cannot view a user's current password. You can only set a new one. WeWeb stores passwords securely using industry-standard hashing.
Letting users change their own password
Users can change their own password through interface workflows using these actions:
- Request password reset — For users who forgot their password (requires email verification)
- Update password — For signed-in users who want to change their password (requires current password)
- Reset password (OTP) — Reset password using an OTP code
When a user requests a password reset, you'll need to handle the On password reset requested Event Trigger to send them a reset link or OTP code via email.
Current user data
Once authenticated, the current user's information is available throughout your app via the auth data in the binding window.
You can bind this data to elements in your interface or use it in workflow conditions and filters.
FILTERING DATA BY USER
A common pattern is to add a user_id column to your tables (using the User column type) and filter data to show only records that belong to the current user. This ensures users only see and edit their own data.

