I'm typing this for @farouqzaib!

I'm faced with a problem where I have to decide who sees what and has access to what. The thing is, it is essentially the same data they'll all have access to but just different actions to be performed on the data. Say,I have a list of contact/phone book directory. A user with admin rights should be able to perform all actions(add, edit, delete e,.t.c), a user with edit rights should only be able to edit a contact while a regular user would only be able to view the contacts. How I plan on implementing this is using something like an access level id which is set when the user(s) register to determine what they see. I can encapsulate the procedure code in a class to make it elegant. That's one solution, I want to know if there is design pattern or something for such problem or if there is a more elegant way of doing that.