Viewer Access

Summary:

Viewer access retrictions

Content (required):

When i use the transaction matching capability for payroll recons it typically contains sensitive data, I have managers who need to 'view' the recon (ie: status and balances) however, do not require access to the detail matching which may contain confidential data. Is there a way to manage this? If i assign a controller viewer access via the org unit, will they be able to drill back to all of the matching detail?

The issue is this makes it difficult for me to provide wide access to status of recon via dashboards while utilizing the detail matching functionality for payroll recons which is a high volume trx area where I very much need that functionality.