I'm in the process of migrating an intranet site from ASP.NET to DNN.

Presently the company has two offices, each with intranet pages that are relevant to it only.  The office's pages need to load by default for its users but the other pages still need to be accessible by all staff. The normal process of assigning View permissions only to one group won't work as prevents them from being viewed by other staff.

Presently I have a custom sitemap provider that XPaths an XML file depending on what office the user belongs to. The file format is similar to the following:

<intranet>

    <office1>

         <page name = "pageone"/>

        <page name="pagetwo" />

     </office1>

    <office2>

         <page name = "pageone"/>

        <page name="pagetwo" />

    <o/ffice2>

</intranet>

This then gets passed into an ASP:Menu as the DataSource parameter.

It appears that I can replicate this with the Menu provider but I need some help on how to do it.

My only two other options as I see it are 1) maintain separate intranet sites and deal with the extra maintenance, or 2) make all pages visible to all users.

Mike

Hi Edmedia

Thanks for your reply. I hadn't given much consideration to applying view permissions at the module level. However, the issue still remains - granting staff from one office only View permissions to content will not allow staff from the other office to view it.

Essentially, I want to display default content for an office, rather than prohibiting staff from viewing content for the other office. This is why the standard solution of applying View permissions doesn't fit my needs.