Page History
...
Table of Contents | ||
---|---|---|
|
Overview
Styleclass | ||
---|---|---|
| ||
...
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.
|
...
See Content Folders for more information.
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 sub folder of the item that is created.
|
...
See Data Sources for more information.
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 authorised 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 |
...
See Field Settings for more information.
Expand | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
|
...
See Access Filters for more information.
Expand | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
|
...