Understanding how to do multiple user tables

Ask the community
1

Hi Softr community,

I’m new to Softr and working through an initial architecture question.

Use case

  • Internal users manage service packages, pricing, and commercial setup.

  • Pricing is agreed per customer and stored against a customer account record.

  • Selected contacts at each customer company then access a portal to place orders.

Current thinking

  • One database seems sufficient.

  • UX-wise, I would prefer two separate apps:

    • An internal commercial app for staff.

    • A customer portal for clients.

  • The goal is clean separation and minimal risk of users seeing things they shouldn’t.

Key question
I’m considering using two user tables:

  • One for internal users.

  • One for client users.

  • Each app would auth against its own user table.

Conceptually this feels cleaner and more encapsulated, especially long term.

Is there anything I should be cautious about with this approach versus putting all users into a single user table with roles?

The only potential issue I can currently see is around fields like Created By, where Softr may expect a single user table. Are there other pitfalls or limitations I should be aware of?

Any pointers appreciated, and apologies if this is a basic question. I’m only a couple of days in.

Thanks

2

In most cases it would make better sense, and be easier, to use two User Groups, rather than two user tables. Different pages/blocks can then have their visibility settings configured to control access, and you can also set data permissions and record level permissions (coming soon).

3

I needed something similar in our use case.
For us the Users have general access and there is a navigation tab that is only accessible to the admin side and there is where we put all of the important pages limited by User Group as Q8T mentioned