Page Comparison

Anchor

	top
	top

Table of Contents

class	contents

Overview

Before deploying Yellowfin to all your users you should determine the security management profiles that you wish to deploy.

...

Do all my users need report writing access?	If no then use your reader role to only allow users with read access to the system
Is the data in my source systems sensitive?	If yes then you will need to apply security to your data source. This will stop unauthorized access to SQL report writers and users that have admin access to the product.
View Security – Is data in my view sensitive. Can all report writers have access to the data contained in it?	If some report writers do not have access to data in the view then view security is required. The security will stop unauthorized reports being written.
The majority of the view is not sensitive but only 1 or 2 columns are.	Define view columns as secure.
If publishing Public reports from the same view will some contain sensitive data and other reports not. For example an HR report containing salaries could be written from the same view as an HR report containing Headcount	If some users should be restricted from the salary data you should create two categories for report saving – one for general access which is unsecure and one for secure access. This assumes that people with report writing access do not have EDIT access to the view – if they do then they could edit a report and add the sensitive data.
Will I be reporting from source systems with completely different subject areas?	Best to set up different categories