I will add a config setting in the next release that will allow you to specify roles that cannnot edit module settings. So you can create a role, put users in it who you don't want to be able to edit module settings regardless of their edit permissions and they won't be able to see the edit link or edit the settings. But it will be across all features not just the blog and of course admins and content admins will still be able to edit even if you add them to the denied role.

Keep in mind the blog feature is designed for "Trusted Users". Users who can make blog posts can put javascript and widgets in the content for good or bad purposes. 

Hope it helps,

Joe

Hi,

Its flexible with what I have done now, by default users in edit roles can edit module settings unless they are in a forbidden role that you put in the config setting.

Sorry if its a little work to get your 300 users configured. 

I'm not going to work on some complex solution to make it per module at this time, don't have the spare cycles to allocate for it right now.

If you have users that you do want to be able to edit module settings then you would not add them to the blocking role.

Best,

Joe 

Under Administration > Site Settings > Security > Permissions

see Roles NOT Allowed to Edit Feature Instance Settings

Hope it helps

Joe