There are a number of ways to filter the data presented to users dashboards:
- Component Filters - Row level filtering of data at dataset level by Component
- Dashboard Filters - Row level filtering of data at dataset level by Dashboard
- Security Filters - Row level filtering of data at dataset level by individual User
The intuitive dashboard system uses the principle of 'shared entities' i.e. shared datasets, components and dashboards. For example, once created, a single dataset can be used by multiple users to create many different components and in-turn a component can be used on many dashboards.
Component Filters and Dashboard Filters limit the row level data that is shown on a dashboard, but they can't dynamically limit the information seen by an individual user when they login to the system.
Security Filters have been designed to achieve this by matching information held against a user (and optionally the groups they are members of), with rows of data from a dataset(s).
By applying security filters at user login, the data presented on a dashboard can be pre-filtered specifically for that user.
Dependent on the specific business need, Security Filters may be very simple to define or can much more complex. The key to understanding Security Filters is to firstly understand the individual aspects of Defining a Security Filter.
Simple Example: User 1 works in the Leeds sales office so can only see Leeds sales. User 2 works in the London sales office so can only see London sales. User 3 is a Sales Manager and can see both Leeds and London Sales. All three users have a separate user login and view the same physical dashboards which are fed by the same underlying datasets, but each sees different data presented, based on their own Security Filter definition.
Note: Security Filters are set-up by the System Administrator when new users are created. When a user logs-in, the Security Filter defined for the that user is compiled and automatically applied to the underlying dataset(s).