Here's the scenario:
A company's sales team is split up into regions with each region targeting a geographic section of the country. Each region is then subdivided into various "districts". Within each "region" the company has a Regional Manager, for each district has a District Manager, and within each district has a number of Sales Reps. There is a direct manager - subordinate relationship between the Regional Manager, District Managers, Sales Reps within the regions and districts.

A K2.Net process exists where the Sales Reps can submit product price quote information to their managers (their respective District Sales Manager) for approval. Based on certain data, this may need to be approved by the Regional Manager.


The problem:
Competition exists between the regions. The CIO does not want one Regional Manager being able to see the workflow items or data that pertain to another region. Security for the workflow appears to be configurable only at the process level. If a Regional Manager is given permission to view the process data, this manager can view the data for all the regions.

There are approx 50 regions so creating separate processes for each region is undesired. There are also other types of processes that need to be created that are also regionaly focused.

How can the visibility of the data be restricted so managers can only see the data for their region? (Managers need to see the data for their region even if they do not participate in the workflow.)