For your 'categories' (would probably call them groups personally), if you expect them to change from time to time, you might want to make a whole group model. otherwise, an enum_string would probably do.
Hobo permissions will handle the field access. The tabs thing will require you to replace the default main-nav tag and conditionally display tabs based on access rights. On Jul 23, 12:09 pm, Arthur Baldwin <[email protected]> wrote: > OK, now that I'm up and running it's time to start thinking about some > practical > solutions to a common problem. > > How would you approach this problem? The hobo app for my company needs to be > "aware" of different categories of users such as: > > Principals > Managers > Accounting > Warehouse > IT Staff > > Depending on which category an employee belongs to, they will have access to > not > only a different set of "Tabs" on the site, but will also have a different set > of database fields to which they have access. This is especially important > when > they are accessing the Employees Table. Any suggestions about how to approach > this? > > Sincerely, > > Arthur Baldwin, MIS Director > The Computer Outlet, Inc. -- You received this message because you are subscribed to the Google Groups "Hobo Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/hobousers?hl=en.
