Security
Again, we have kept things simple without sacrificing power. The DataWarehouse Explorer has been designed to fully exploit the native Windows security schemes and therefore there is no need to define security settings for DWE separately. In most organizations, every employee is assigned a user account with a set of permissions. As these permissions propagate into DWE, starting the application does not require a username or password.

Administrators simply assign permissions on files and folders to individual users or groups of users. When users do not have read access to a report or group of reports, they will not be visible to the user from within DWE. It’s that simple. When a user or group of users are allowed to read a report, but do not have write permissions, the option to save this report will be disabled.

For reports stored on a DWE Portal, defining permissions is performed in the same way permissions are defined on a file share. Again, using the native windows user/group account to base the permissions on.

The administration of permissions as well as the distribution of new reports can be performed while users are working with the Data Warehouse Explorer. All changes are dynamically reflected in the DataWarehouse Explorer interface, thus guaranteeing an up to date situation at all times.

Data-level security (at the record level) can be administered by the tools supplied with MS Analysis Services (for Olap) or RDBMS vendor (for tailor-made reports). This enables administrators to define detailed security rules, e.g. that information regarding sales in Europe should only be available to the sales department that is responsible for Europe. The DWE does not need to know about these rules, it will follow them transparently.