User vs Staff: one database or two

khalidradwan10 · 2025-02-05T06:14:36.695Z

Hi everyone,

I’m developing an app that allows companies to register their staff details, including name, phone, email, date of birth, and more. Some staff members will need system access (i.e., users), while others won’t.

I prefer not to use Bubble’s “Create an account for someone else” feature since it requires every staff member to be a user with an email and password, which may not be convenient for all. Instead, I want to support both:

Passive users – Staff members stored in the database without system access.
Active users – Staff members who have system access.

What’s the best way to implement this?

johnny · 2025-02-07T00:28:10.349Z

You can use create an account for someone for those who need an account and don’t for those who don’t

I would store both in a separate data type from the default Users one.

khalidradwan10 · 2025-02-07T05:43:55.630Z

So, you suggest to have Current user (master admin, first person who subscribes), Staff (every employee in the company) and Users (staff with access)? If so, why can’t I have two types: Staff and Users, where Staff is everyone whether with or without access and users is staff who has access. Just thinking…

johnny · 2025-02-07T06:00:16.869Z

That’s what I’m suggesting

User would be the staff with access

Staff would be both

system · 2025-04-16T06:14:50.230Z

This topic was automatically closed after 70 days. New replies are no longer allowed.