Take a look at this in the cookbook: http://cookbook-staging.hobocentral.net/manual/permissions
On Jun 24, 7:51 am, Owen Dall <[email protected]> wrote: > The Hobo permissions system can handle that for you. I need to fine an > example...someone else will probably beat me to it... > > > > > > On Thu, Jun 23, 2011 at 11:54 PM, ylluminate <[email protected]> wrote: > > I have a scenario where there are details about a model that are to > > ultimately be kept from public consumption and only visible and > > alterable by the administration. Traditionally I would put that into > > a "detail" or hidden table that belongs_to the parent table so that > > only the parent table or model and it's contents are visible to the > > public. Presently I had some complications with this detail table in > > terms of ActiveRecord inheritance and so I simply integrated these > > details into the main model... > > > Is this a problem or is there a way to limit specific fields in a > > table/model based upon user types (authenticated vs not authenticated > > for example)? Otherwise I'll have to rethink the model relationships. > > > Thanks! > > > -- > > 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. > > -- > Owen Dall, Chief Systems Architect > Barquin Internationalwww.barquin.com > Cell: 410-991-0811 -- 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.
