We are attempting to setup DNN such that certain users will have their own personal pages to which they can add any module they wish from a set they have been granted permission to.   The first half of our objective has been accomplished.  We can give the users in question the "Add Content" permission for their personal page and give them the "Deploy" permission over the modules we want them to have access to.  This allows the user to add new modules.

This is fine, but what we need primarily to do is allow them to add existing modules from other pages to their personal page.  For example, they may want to add the announcements module from the site home page to their personal page.  The basic rule is that they should be able to add any module that they can view elsewhere to their personal page, and once added to their personal page, they should have the same permissions over it there as they would have over it on the original page.

What we have found is that to enable this we must do the following:  The user must have the "copy" permission for a page in order for that page to appear in the Page: drop-down for adding existing modules.  This is okay--we can live with it--but it seems that if they have "view" permission to a page, it should appear in this list.  Beyond this, in  order for a module to appear in the Module: drop-down, the user must be granted full control to the module on the source page.  This is not something we can live with.  Again we feel that if a user has view access to the module they should be able to add it.  Short of modifying the source code, is there any way to affect these changes?

It should be noted that we are using an evaluation version of DNN 5.6.1 Enterprise.

--Ken