3.2.3. Reports

The reports created in MicroStrategy must be saved in on of the following folders:

• "Public Objects/Reports" (or a subfolder of this): in this case the report will be visible to all users who have access to this project;

• "My Personal Objects/My Reports" (or a subfolder of this): in this case the report will only be visible to the current user.

You cannot view reports/documents from folders other than those mentioned above.

Configure Report View

The groups/users created in MicroStrategy do not have access to any project, thus, by default, a user cannot view any report. The access to projects must be manually configured in MicroStrategy. It is recommended you do this at group level (corresponding to the SocrateCloud role).

Furthermore, in MicroStrategy a user must be granted access to a project through a single group. This requires the identification of the roles necessary for reporting in MicroStrategy so that one does not reach situations where a user has two or more roles with MicroStrategy reporting privileges all of which having access to the same project. Otherwise, when running the reports in that project, the data that the user will view in those reports will be the result of unifying all the Security Filters from those groups, irrespective of the role that the user has logged into SocrateCloud with.

Note: For further details on how MicroStrategy unifies the Security Filters for a user, please see the MicroStrategy documentation "System Administration Guide Volume 1", chapter "SETTING UP USER SECURITY" > "Restricting access to data: Security filters" > "Merging security filters".

In order to understand why it is necessary for a user to have access to a project in MicroStrategy via a single group, let us take the following example:

The user U1 in SocrateCloud has been assigned the roles R1 and R2, both of which making up groups in MicroStrategy. Thus, there are two groups in MicroStrategy with the same names as those of the two roles.

For a project P1 in MicroStrategy, each of the two groups have their own Security Filter.

Let us assume that both groups are granted access to project P1.

User U1 logs into SocrateCloud with role R1 and wishes to run a report from project P1. The moment the report is executed in MicroStrategy, you can no longer make the difference if the user has logged in with the role R1 only. Consequently, MicroStrategy will execute the report and apply the Security Filters from both groups (unifying these by following the rules described in the MicroStrategy documentation).

Report View

The reports can be viewed in the web browser starting in SocrateCloud from the list of reports available to the user-role combination. If the report cannot be viewed due to the fact that the MicroStrategy session has expired (a message will be displayed in the web browser) it is necessary to reload the reports list in SocrateCloud.