Merge - 2nd Level Navigation

Question

Hi there
Would really appreciate it if someone out there can put me out my misery.
Here follows the problem ...
The requirement on this project is to have really fine control over which reports users are shown. To this end, reports (iviews) are assigned to roles. Users are then assigned to the relevant role to give them access to the required reports.
In terms of the menu structure, many roles make up a menu. In order to not display menu items to which a user has not been assigned, we have gone with the merging approach.
Anyone out there know how to merge on the second level of navigation?
R1 = required top level tab
R2A, R2B = required second level tabs
R3A1, R3A2, R2B1, R2B2 = required detailed navigation items, each with their own structures defined with worksets
At the moment, R2A and R2B are assigned as delta links to R1.
R3A1 and R3A2 have the same mergeID as R2A. R2A has the lowest merge priority.
Similarly, R3B1 and R3B2 have the same mergeID as R2B.
For now, the test user is assigned to all the roles above, just so that I can see if the merging works.
The theory goes that if this works, I can assign the user to the relevant R3? roles and they will then only see what they are supposed to see.
All I see however, is R1, with R2A and R2B on the second level, but none of the lower roles pull through to the detailed navigation.
If I set R2A and / or R2B to be entry points, then they show as a top level tab, and the R3B1 and R3B2 roles are merged correctly underneath.
If I make them not entry points, then I don't get any merging.
Any ideas ... anyone follow what I am saying ... very difficult to explain this in text without drawings
Cheers,
Andrew

Answer 1

Andrew, Steve and Selvaraj,
Here is my work around. It's not easy to maintain, but it fulfills the requirement..
We can only merge roles appropriately in the 1st level, when we make them entry points right? If we add them to another role as delta link, whether they have inner role or not they see the roles content. Also we dont want their content to be seen in the second level.
My solution is again merging them in the first level and make them entry points with lower merge priority then our original entry point. However add our second level roles one folder with the same name and merge them with the 1st level role with the same id and make entry point.
The result is
My job
---My applications
App 1
App 2
Now the roles
roleMyApps : mergeID=mergeApps Entry point, priority:1
roleSalesPerson mergeID=mergeApps Entry point, priority:5, containing a folder named (my applications) * its the trick, and under it your original content.
roleFinancePerson mergeID=mergeApps Entry point, priority:5, containing a folder named (my applications) *, and under it your original content.
You can also use worksets rather then folders but I didn't try it.
Let me know if it helps, and reward helpful answers.
Regards,
Barış