I can get you part way there. I'm a little unsure of how to approach that use of XML, but here's the larger outline of what you're going to do.
ASP.NET has a Membership provider that allows you to assign different security roles to various users. Among others, it sounds like you'll want to assign at least two roles, Agents and Managers. Then you will add a LoginView control to the page, and set it's properties so that only Managers have access to the contents of the LoginView. Then code items available to everyone outside of the LoginView control, and code items available to Managers only inside the LoginView. You can insert as much or as little of the page inside the LoginView, depending on what you want available to Managers only. If the whole menu should be restricted, place the entire menu inside the LoginView. If say, only the 2nd and 5th items on the menu should be restricted to Managers, you would start writing your menu code, then have a LoginView wrapped around the 2nd item, then the 3rd and 4th menu items, then another LoginView wrapped around 5th item.
Now since the menu's being pulled from an XML file this will get more complicated, because your C# code is going to have to grab the menu code and then start processing it to apply the LoginView in places where you want it, and not in the places that you don't. I'm guessing you're going to need a for each loop to go through each of the menu items and see if they are available to everyone or not. This would be where I'm a bit sketchy on the implementation. But that's the general outline of what you want to do. You might want to spend some time with the membership provider. This is just a relatively limited application. You can actually do some much more complicated things using LoginViews and other controls for very advanced designs.
For example, you might want to abandon this whole approach and simply investigate how the Membership provider can allow you to use "security trimming". If you use a sitemap file in your web application which lists the roles that each page is available to, the default navigation tools (SiteMapPath, Menu, etc.) automatically provide the kind of behavior you're looking for. Simply drop the navigation control where you want it in code and specify the sitemap for it to use as a source. Then you'll get rid of the XML document with your menu information and recode that in a *.sitemap file (which is also in XML, it wouldn't be much different than the structure of your current menu).
Just a couple ideas.
-------------------------
Whatever you can do or dream you can, begin it. Boldness has genius, power and magic in it. Begin it now.
-Johann von Goethe
When Two Hearts Race... Both Win.
-Dove Chocolate Wrapper
Chroniclemaster1, Founder of
www.EarthChronicle.com
A Growing History of our Planet, by our Planet, for our Planet.
How to create progrmmatically Menu tab using XML i
