A powerful feature of Interactive Reporting is the ability to take data “on the road.” Once data has been extracted from the database, which is where the row‑level security restrictions are enforced, that data can be saved with the Interactive Reporting document for offline analysis and reporting. Users who publish should be aware of the implications of their audience when publishing data and reports.
If the publication of the data is difficult to control in the current configuration of users and groups known to the server, consider the following options:
Publish without the detailed results of the queries, leaving only the summary charts and Pivots for the “general” audience. If they need to drill into the summary data, they will need to rerun the queries, at which time their particular security restrictions will be applied. (Even some charts and Pivots can reveal too much, so there is still a need for prudence when publishing these Interactive Reporting documents).
Create theInteractive Reporting documents with OnStartup scripts to reprocess queries as the Interactive Reporting document is opened. This option provides the user only the data to which they are entitled.
All users should take similar precautions when sharing information generated from Interactive Reporting. This includes exchanging the Interactive Reporting documents (BQY extensions) themselves by e‑mail or shared network directories, exporting the data as HTML files and publishing them to a web site, posting the data on FTP servers as the result of a job action, and creating PDF files from the reports.