#custom fields user table

17 messages · Page 1 of 1 (latest)

spare wind
#

hi, what you guys recommend me for this?

i have a php system without any framework
i want to migrate to filament
currently it have two tables one for admin login, one for client login

should i have the same in filament? i mean two diff table for login? the difference is the client table have many custom fields like address, identification, passport, phone, mail, services, mobile and so on that admin table doesn't have. or should i use one table only of users and have a client_detail table for example with a foreign key that links to the user table?

thank you

cerulean bearBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

valid panther
spare wind
#

so in my users table i need to create the 20 custom fields?

#

what about the page to create users, should i have two? one to create regular admin users and other for clients? as i dont want to see too many fields when creating admin for example

#

sorry to ask too many questions, im trying to replicate my current php app (i dont have source code) so we are wanting to move slowly to filament from a pure php app that is like 15 years old

valid panther
spare wind
#

ok

#

not sure if i understand, but in that case it shows user model and phone model so two db tables right? or im missunderstanding the concept.

valid panther
spare wind
#

oh got it so a regular user and maybe a client_details table with the relationship and primary key

#

to get all details

#

and regards the page to create edit? should i have one for admin and one for regular clients so i can show the fields according

cerulean bearBOT
spare wind
#

i was confused and you said keep a single table

#

but now im clear i keep one table for users in general and another for client details

valid panther