Page History
...
A role is a collection of available security functions. Each user will have a role associated with them. As the Yellowfin report writers you can either:
- Change a person's person’s role - – and thus the type of access they have to the application or
- Change a role definition by adding or removing functions and thereby updating all users' users’ access to the system that share that role.
When a user is logged in the system checks that they are still registered in the application and if so what role they should have. Based on the role access the users interface will be dynamically built - – only showing them links and functions that their role has access to.
See Roles for more information.
Expand | ||
---|---|---|
| ||
If a |
...
user’s role does not have access to the dashboard when they login they will be taken to the report list page. A user with dashboard will be taken in to the dashboard page.
|
...
|
Report Categories
Styleclass | ||
---|---|---|
| ||
...
Expand | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Rather than having to specify who is allow to see a specific reports each time you create a new report the security for the report is inherited from the subcategory of the item that is created.
|
...
Expand | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
If the HR system is to be setup as the source system any user with View Definition access will be able to view all tables including payroll data if the source is unsecure. By securing the source to only HR view builders, only those authorized users will be able to define and manage the HR related views.
Note: If there is only 1 Yellowfin report writers of your Yellowfin deployment, and no additional users writing SQL reports then you may consider leaving your source systems unsecure |
...
Expand | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
The Finance view is created. Only the finance department is permitted to write finance view reports. In this case the view would be defined as secure and the finance users would be added into the access list with edit access.
|
...
- Create a copy of the view and exclude the salary column from this instance. Save the view with a new name to indicate that the view is free of sensitive data.
- Alternatively Yellowfin provides you with the opportunity to define the columns as restricted columns. Once this has been done an additional layer of security needs to be defined, which allows certain users access to the restricted columns of the selected view.
Note: security to restricted columns is globally defined. You cannot specify different users for separate restricted columns within the view.
Only users with restricted access will be able to see the item when creating reports. When an active report is run, restricted columns will be displayed to all users who have access to the report.
...
In some cases a view might be created that is designed for general use but you only wish report consumers to access data from the view that is relevant for their position in the organisation - – such as cost centre manager. In this case you would create an Access or Value based filter.
This is achieved by updating the source connection wizard to specify the available filters - – such as cost centre and your users' users’ relationship to that source. You then specify the specific columns on the view that related to that source filter - – e.g. you must indicate which column in the view is the cost centre column.
...
See Source Access Filters for more information.
Expand | ||
---|---|---|
| ||
|
...
|
horizontalrule |
---|
Styleclass | ||
---|---|---|
| ||