Table Permissions for Database Roles - Why do I need to GRANT CONTROL permissions as well as SELECT

I am trying to granularise my permissions for each of my tables. So that my website users can for instance only run a select statement against a particular table under their user profile ABC123 (which is attached to the website users database role).


However this seems to be less straight forward than I expected it to be.


e.g. fortblSessionID I had to grant 'CONTROL' permissions aswell as INSERT and SELECT.


I am not sure what setting the CONTROL permission to GRANT does.


Can you tell me why I have to tick the GRANT box for CONTROL permissions in order for the user to obtain SELECT permissions, I don't want to give them more permissions than is necessary? I have looked up Explicit permissions and the CONTROL setting in particular and found nothing to help me.


I have attached a screen shot of my permission settings.


Any help will appreciated, thanks.

 

Anyone out there who can help, pls?

 

Thank you for your helpful reply.


I guess I am going to have to have a further play with a test db to see if I can achieve this. At present I can't on my discount asp hosted db.