Defining two user types in the DB

Hi everyone,

My own Christmas gift is a wappler subscription this month! I’m finishing reviewing a few webinars/tutorials and I’ll join for a project. But a question remains:

I’m going to build a platform matching users seeking help and consultants.
I have a general users table with info that is common to both users and consultants (fname, lname, emails, pwd, and is_consultant boolean field 0/1) and a consultant table (with a user_id as FK) with info pertaining to consultants only (title, category, bio, pic…). Users must signup for browsing consultants detailed bio, messaging them internally, submitting tenders,… Consultant with a profile will have their own dashboard, can reply to users’ tenders,…
Can the boolean system do the work of controlling info access like user’s access to consultant’s bio for example and features like consultant’s bidding on user’s tenders or is it better to create a table for defining roles (U for users seeking help and C for consultants) based on @Hyperbytes websinar?

Thank you!