How do I assign "edit in place" permissions for the Module Title to a new security role?

I have created several security roles, each responsible for the content in it's portion of a site.  By assigning "edit module" permissions to the respective roles each can edit as needed.  The only exception to this seems to be the Module Title Skin Object's permissions seem to be set to admin and host by default and do not apply to any of the "new" security roles

How do I allow a "created" security role to edit the Module Title using the "edit in place" functions?  If I assign "edit page" permissions to a role at the page level, then that role can edit the Module Title, but not if I only assign "edit module" permissions at the module level.

If I edit the Title.ascx file I can assign edit permissions to the whole world, but not to a specific role.  That obviously isn't optimal.  Am I missing something really simple.  I have looked all over the boards to find the answer and don't seem to find it.  I know it has to be something really simple.

Clay

Thank you for the reply. If permission is bound to "edit page" permissions, is there a way to create a role with "edit page" permissions and no access to the control panel?

Seems like I have seen a few threads on that, but never saw an answer to that question either.

It would be nice to allow "edit page" but to disallow adding or deleting modules.  Sort of a restricted use Admin role.  I don't mind them having access to rename the page, or even to changing it in the heirarchy of pages, but allowing these particular users the ability to delete or add pages or modules simply is not acceptable.

Any Ideas on this?

Clay

Thanks FX,

I'll take a look at it.  Module only permissions isn't viable as the user cannot change/edit the module title.  That is the reason I started down this road.

I did find a module by dnnmasters that comes close and one by arrownuke (Custom Control Panel) that does what I need, but only by portal, not by portal user.  I can live with the latter though. 

For now, I have a simple solution that autohides the control panel (from Nik Kalyani at DevTao (tutorial and download)) that I modified so only an admin who knows where to find the activation can open the panel to use it. 

I'll probably settle for one of these as a permanent solution.

Thanks again for all the help.

Clay