Feature feasibility with Weweb

Ask us anything How do I?
1

Hello,
I’d like to study the feasibility of a feature with Weweb.
Let’s say I want to create a SaaS CRM.
In a contact details page, I have 10 different fields (all linked to my database). Could each user choose the number of fields they want to display ?
Example: customer 1 wants to display only the first name and last name. Customer 2 wants to see all the fields.
Also, can these customers create a new fields by their own?

Thanks :slight_smile:

2

I think that is you are trying to build Salesforce, where the user has the option to create their own fields, you may get into some trouble.

But if you are building a defined solution with some individual user visibility permissions, then it should be fairly easy. You need to hold the visible/not visible relationship between the fields and the user. Then use conditional formatting.

This would a way of doing it. I presume that there are multiple ways to address this.

1 Like
3

Thanks for your quick answer.
Actually it’s a CRM built for Schools where each school can choose to add a field in certain pages (contact detail page for example). The visibility permission will be at school level.
My question was more regarding the feasibility of : it is possible to allow admin users of each school to add new custom fields in certain defined pages of their application ?

4

Everything is possible, usually it’s a limit of the developer, not the platform.

1 Like
5

Hey Julien, welcome to our community :waving_hand:

Yes, this is definitely feasible with WeWeb and a backend like Supabase.

You can:

• Allow each school to define which fields are visible on the contact detail page;

• Store those field visibility preferences at the school level;

• Use conditional display logic in the WeWeb Editor to show or hide fields dynamically based on those settings.

For custom fields created by schools:

• You can support this by having a dynamic schema setup, where schools define custom fields and values;

• These fields can be stored in a JSON column in Supabase or managed via a separate custom_fields table that links back to the contact.

The second option will be a bit more complicated but doable.

Hope this helps :slight_smile:

2 Likes
6

Thanks for your reply :slight_smile:

1 Like