Database design for role security table

Question

I am looking for some direction on creating my person, role classes and teh design of the tables.

 

I am looking to implement security that will allow the role to be set to Add, View, Delete, Print for each specific area.  I think the easiest way would be to have the table

(RoleId, ContactAdd as boolean, ContactView as boolean, ContactDelete as boolean, ContactPrint as boolen, ActivityAdd as boolean, ActivityView as boolean, ActivityDelete as boolean, ActivityPrint as Boolean)

 

Or (RoleId, AreaId, Add, View, Delete, Print)

(1, Contact, True, False, True, False)

 

But then when I create my class do I create the Role and then assign these as properties, going out to the database for each Area ID.

 

Role.Contact.Add = True

 

Thanks for the assistance, and if you know of any examples those would be very helpful!