Ramon Tayag wrote:
> I would separate it... keep the roles and permission you have with
> activefx's tutorial.  Then your
> 
> group or channel
> has_one :administrator, <necessary options here>
> has_many :notables, <necessary options here>
> has_many :members, :through => :memberships, <other necessary options 
> here>
> has_many :memberships
> 
> Maybe even the membership model can contain what capacity the user is
> in the group?  This just popped into my head now.. not too sure if
> this would work.  Sounds okay though.
> 
> On Wed, May 7, 2008 at 5:03 PM, Neil Cauldwell
> <[EMAIL PROTECTED]> wrote:
>> my Roles table simply has Administrator, Notable, Member (for Site,
>> Firstly, do I need to avoid mixing site permissions in with object
>>
>> >
>>
> 
> 
> 
> --
> Ramon Tayag

Thanks, Ramon. This is quite an old post - I've been happily working 
along with permissions for a while now. In fact, right now, I'm 
integrating per-permission notifications options, whereby a user can 
specify which activities they want to be notified about (email) on a 
per-group basis.

If you're interested, I posted a question about notifications & 
named_scopes, in Railsforum a couple of minutes ago. I've since found a 
solution for the first question, but, I know there's room for 
improvement;

http://railsforum.com/viewtopic.php?id=22509

Also, my friend Ryan, from ThinkRefresh.com, made a screencast about 
polymorphic permissions after I posed the same question to him;

http://thinkrefresh.com/posts/7/polymorphic-permissions

Maybe that'll help anyone else who comes across this post...


-- 
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" 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/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to