Your users and your mailing list, kept apart and linked.
App users, workspace members and marketing contacts are separate records, so deleting a newsletter contact never touches anyone's account. Your app stores what it learns about a user as attributes, and you group contacts into smart lists that email campaigns and workflows can send to.
Your app is an organization in BuildBase. Your users sign in and work inside workspaces - one per team or customer.
You set up
In the console and the SDK
- The details you want to remember about each user, like onboarding done
- Lists of people to email, by hand or by filter
- An import of your existing mailing list, from a CSV
You get
For you and your team
- A record of every user, their devices and their activity
- Lists that keep themselves up to date for campaigns
- The power to sign out a device or block an account
The people tables you would otherwise design
Accounts, attributes and marketing contacts are already modelled and connected to email and workflows. You decide what to store.
Users and Contacts, Apart
Your app's users and your mailing-list contacts are separate records: blocking or unsubscribing a contact never touches an account. A contact with the same email as a user is linked to them for you.
Remember Anything
Save details your app learns about a user - onboarding done, plan interest - and read them back anywhere in your app.
See When It Changed
Every change to those details is recorded, so you can see when a user finished onboarding, not just that they did.
Lists That Update Themselves
Build a list from filters - tags, details, who opened a campaign - and it refreshes every hour.
Bring Your List
Import a CSV, match its columns, skip or update duplicates, and export any filtered list back out.
Look After Accounts
See a user's sessions, devices and emails, sign out one device, or block the account without deleting it.
Attributes from a hook
useUserAttributes() reads and writes the signed-in user's fields, and every write lands in the history.
import { useUserAttributes } from '@buildbase/sdk/react';
export function OnboardingGate({ children }: { children: React.ReactNode }) {
const { attributes, loading, updateAttributes } = useUserAttributes();
if (loading) return null;
if (attributes.onboarded) return <>{children}</>;
return (
<button
onClick={() =>
updateAttributes({
onboarded: true,
plan_interest: 'scale',
seats_estimate: 25,
})
}
>
Finish setup
</button>
);
}Look after every account from the console
The support and admin screens a user table needs, already built, so a locked-out customer or a move from another provider is a few clicks, not a project.
A page for every user
Everything about one person, in one place: their profile and what's verified, tags, custom details (claims), feature flags, workspaces and lists. Below that are the emails and notifications they were sent, their activity, devices and sessions, workflow runs and their own plan.
Block, sign out, reset
Block an account without deleting anything. Sign someone out of one device, or end a single session. Reset two-step sign-in for someone who lost their phone.
See what they see
Open your app as that user, straight from their page, to see what they see. It's read-only by default and lasts 5 to 60 minutes. The audit log records when you started and whether you left early. Needs @buildbase/sdk 1.0.0 or later.
Import accounts, not only contacts
Move real user accounts over from Clerk, Auth0, Firebase or Supabase with one command. Passwords kept as bcrypt, Argon2, PBKDF2 or Firebase scrypt keep working, and verified emails, phone numbers, old IDs and social sign-ins come too. Auth0 hands over hashes only when you ask its support.
Deletion that keeps the history
Deleting an account wipes its name, address, phone, ways to sign in and devices. Its past activity stays, under "Deleted user", so your reports and audit log still add up.
Every account change on your webhooks
Your other systems hear about 24 kinds of account change as they happen, by webhook (a message sent to your server) or as a workflow trigger. They range from a sign-up or an import to a blocked account, a changed email, two-step sign-in turned on and a deletion scheduled.
Works well with
Other modules for users & access.
Read more in the docs
Setup guides and reference for User & Audience Management.
Overview
User profiles, smart lists, and attribute-based audience segmentation.
User attributes
Store and update custom fields on the signed-in user, with a full change history.
Audience and lists
Manage marketing contacts, tag and segment them, and import a CSV in three steps.
Importing users
Move user accounts from Clerk, Auth0, Firebase or Supabase with their passwords and social sign-ins.
Signing in as a user
Open your app as one of your users for support, read-only by default and recorded in the audit log.
Deleting accounts
Let people delete their own account, with time to change their mind, and see what a deletion removes and keeps.
Managing members
Invite members, assign roles, and track seat usage.
Admin API
Authenticate with an org API token and call the REST API behind the console modules.
Frequently Asked Questions
What people ask about Users.
Do my users see this?
No. This is your team’s view of the people using your app and of your mailing list. Your users only see their own profile.
What is the difference between a user and a contact?
A user has an account in your app. A contact is someone on your mailing list. They are separate records, so deleting one never deletes the other, and you can link the two when they are the same person.
How do I store details about a user?
From your app with useUserAttributes(), or in the console. Define the keys in the console first so lists and workflows can filter on them.
Can I import my existing users?
Yes, both user accounts and mailing-list contacts. Accounts come from Clerk, Auth0, Firebase or Supabase with one command, npx @buildbase/sdk import. Their password hashes, verified emails, phone numbers, old IDs and social sign-ins come with them. Passwords in bcrypt, Argon2, PBKDF2 or Firebase scrypt keep working; Auth0 hands over hashes only when you ask its support, and anyone else sets a new password with Forgot password. Contacts come from a CSV file: you match its columns to your fields and choose what happens to duplicates.
What can my team do for a user who is locked out?
From the user's page in the console, your team can unblock them, sign out a lost device or a single session, or reset their two-step sign-in after they lose their phone. They can also sign in as the user, read-only, to see what they see. Your app needs @buildbase/sdk 1.0.0 or later for this.
Start remembering things about your users
Define your attributes in the console, then read and write them with useUserAttributes(). When you are ready to email your existing list, import it from a CSV.