I just upgraded to 4.5.5.  I set page permissions for a user to be able to view and edit the page (not a role, but typed in the username and added them then clicked view and edit).

That user logged in and was able to add a module to the page, but the module did not inherit the view and edit permissions.  So the user can add a module, but then not do anything with the module!

Is this a bug or is this by design?  Is this fixed in 4.6.2?

You wouldn't happen to have the logic behind that decision would you?

We have school teachers that trust me, it is hard enough to get them to understand how to add a module.  But then to tell them that they have to click on settings, add their account name and add it, then click on edit, then Update, just so they can edit the module they added, seems like a LOT of steps.  Wouldn't it make more sense to give the person adding the module the rights to edit that module (not just the settings, but in this case Edit Text)? 

It just seems like poor design from my perspective, but maybe there is another perspective.

We should have the option to inherit both view AND edit permission from page down to modules and that should include role based and indiviual based permissions.  That would include new modules being created inheriting the page permissions if that option is set at the page level.

ETA:  Why is there inherit view and NOT inherit edit as an option anyway?  doesn't make any sense to me.  And inherit view doesn't even technically work since it only does roles now, not individuals.

ETA:  Also, the problem with role based permissions is you have to create roles for an individual and that is redundant.  We have a LOT of pages where only one person can edit.  I was so excited with 4.5.5 that we no longer had to create a user, then a role for that user, just to let them edit pages.  Turns out we should have stuck with that I guess.