In the last app I made it was fairly straight forward. Front end for
users, admin area for admin.
This app is a little more complicated and I wanted your opinions on
the best strategy.
The site will have Site Admin (myself and moderators.)
Dealers may sign up to the site and have there own
"Storefronts." (store fronts may have only one owner or master admin
but multiple users for maintenance)
the Dealers require a smaller admin section for there storefront.
Customers may come and browse the entire site including all available
Storefronts.
Would it be better to run two different logins with 2 different user
tables? SiteWideAdmin and Dealers. Or one master login with one user
table and allot of permissions & roles spread all over ?
In the last app I made it was fairly straight forward. Front end for
users, admin area for admin.
This app is a little more complicated and I wanted your opinions on
the best strategy.
The site will have Site Admin (myself and moderators.)
Dealers may sign up to the site and have there own
"Storefronts." (store fronts may have only one owner or master admin
but multiple users for maintenance)
the Dealers require a smaller admin section for there storefront.
Customers may come and browse the entire site including all available
Storefronts.
Would it be better to run two different logins with 2 different user
tables? SiteWideAdmin and Dealers. Or one master login with one user
table and allot of permissions & roles spread all over ?
The latter. Users are users so why complicate it with extra tables
and models, along with duplicated code? Just add to the available
roles to provide the access you require.