How to manage customers in Bubble

To manage customers in Bubble, you usually create a User data type, add fields that describe the customer, protect that data with Privacy Rules, and build workflows that create, update, and retrieve customer records in a controlled way. Bubble already treats every logged‑in person as a User, so “customers” are usually just Users with extra fields.

Core Structure

Create customer fields on the User data type. Typical fields are name, phone, is_active, customer_notes, and anything else you need to show or filter. When you sign someone up, Bubble automatically creates a User record. When you need internal customers (not app users), you create a separate Customer data type and link it to a User when needed.

• User: Built‑in type used for customers who log in.
• Customer: Optional custom type for customers who don’t log in.

Privacy Rules

Use Bubble’s Privacy tab to restrict who can see customer data. For example, create a rule “When Current User’s role is admin → View all fields”, and a default rule that hides sensitive fields like email, phone, internal notes.

• Check Find this in searches only for roles that should list customers.
• Hide fields like email or notes unless the User is allowed.

Creating & Updating Customers

Use Workflow → Data (Things). If customers log in, use “Sign the user up”. If they don’t log in, use “Create a new Customer”. To update, use “Make changes to User” (or Customer).

// Example: Backend workflow to update a User's status
Make changes to User (thing = User from URL parameter)
field: is_active = yes

Displaying Customers

Use a Repeating Group with Type = User (or Customer) and Data Source = “Do a search for Users”. Add constraints like is\_active = yes. Privacy Rules determine what fields appear.

• Set Repeating Group cells to show name, email, status.
• Use a “Show popup” action to edit a customer.

Using Backend Workflows

For automated tasks (renewals, reminders, cleanup), use the backend. For example, schedule a recurring workflow that checks which customers are inactive.

// Example: Backend search
Search for Users
constraint: last_login < Current date/time +(days): -30

This setup lets you reliably store, protect, edit, and automate customer management inside Bubble without hacks.