I was wondering from your last posts why it was you needed so many access levels. So you actually have over 50 different committee pages, all with different sets of members.
Just a thought, but how different are these committee pages. have you thought about just creating a committee page template, and populating it with database information?
That way if a user selected "Committee A" the page would load with only Committee A information, and so forth. Now you basically only need one page or set of pages and a single rule. Other than restricting access to the page for members, the security comes in by associating which committees a particular member belongs to in the user profile table.
The way it would work, in the user profile page there's a section called "My Committees" with a list of commutes associated with that user. Each listing would link to the main Committee page, and pass the Committee ID in the link. The target page would use the ID to create the recordset to populate the page with the database info from that committee record.
There are other ways to secure it even further. Such as passing a form variable instead of a query string where the ID would appear in the URL.
You could also create another single rule, or basically make it yourself, on the Committee oage. In essence, it would create a reforest that committee IDs that are contained in the user profile, and compare them to the current committee ID that is poised to populate the page. I believe this could be done using SA, nut I haven't tried something like this using dynamic data. But if there are marches when the comparison is made, the user gets kicked out to another page.
Sorry for another long winded confusing alternate solution. It would depend on whether the various committee pages could be built in a similar layout, and I am assuming that each page now is a separate page with static content.
But if everything is working for you the way you want it to, this may be something to think about for the next version. The results would appear practically the same, but it would be overall more efficient and much easier to maintain once it's all set up.