Managing the Report Server in .NET framework

Print QR Code 2d barcode in .NET framework Managing the Report Server

3. Click the Configure Site-Wide Security link. The System Role Assignments page is displayed:

Notice the default system role assignment of the local system administrators group, BUILTIN\Administrators, as System Administrator. You ll always need at least one System Administrator role assignment. 4. Click New Role Assignment on the Report Manager toolbar. The New System Role Assignment page is displayed:

10:

As with item-level role assignments, you can assign a user or group to multiple roles. If you select the Role check box above the list of roles, you can select all roles. You can also add another role by clicking New Role, or edit the existing roles by clicking the role link. 5. Click the System User link. 6. Click Copy. A new role is created with the same tasks that are assigned to the System User role. 7. Enter a name for the new role: Shared Schedule User. 8. Add a description that details the assigned tasks: View shared schedules. Tip By listing the tasks in the description, a System Administrator won t have to open the role definition to see the task assignments in the New System Role Assignment page.

9. Clear the Execute Report Definitions check box and the View Report Server Properties check box. Your screen should look like this:

You can also add a new system role or edit an existing system role whenever necessary by using the Site Settings link at the top of any Report Manager page. Click the Configure System-Level Role Definitions link to access the System Roles page.

Part III:

11. In the Group Or User Name box, type AWSalesAnalyst. 12. Select the Shared Schedule User link check box. Your screen looks like this:

13. Click OK. The System Role Assignments page is displayed:

Now the AWSalesAnalyst role can use shared schedules with the reports it can access as defined by item-level role assignments.

10:

Sometimes different users need access to the same report, but each user is allowed to see only some of the data. For example, a sales territory manager might be allowed to view only data that pertains to his or her sales territory. In this case, using item-level security works only if you create a separate report using a different query in each report to restrict the data to a single sales territory. If many reports require a similar separation for different groups of users, the administrative overhead of maintaining and securing all the variations can quickly become overwhelming. Instead, you can choose a technique that leverages the use of one report, yet still satisfies the requirement to restrict data by user. The simplest way to restrict the data a user can see in a report is to use linked reports with parameters. Using this approach, you can easily control which data is displayed in the report, and then use item-level security to control access to each linked report. Alternatively, you can design a report that takes advantage of the User function from the global parameters collection to identify the current user. You can pass the user identification either to a query parameter or to a filter to restrict the data in the report.

As you learned in 7, Building Advanced Reports, you can use a report parameter to filter data at the source with query parameters or to filter the report data after the full dataset has been retrieved. You can then set a different parameter value in each linked report, which you learned how to do in 9. By removing the parameter prompt, you prevent users from changing the parameter value and thereby restrict the report to the data defined by the parameter value. You can store each linked report in a separate folder to which you add role assignments to secure access, or you can add role assignments to each linked report to manage security at the report level. In this procedure, you ll create a linked report from the Actual Vs Quota report, using a parameter and item-level security to restrict access to user EuropeDirector and local system administrators. Use a query parameter in linked reports to restrict data 1. If the Report Manager isn t already open, launch it in Internet Explorer at http: //localhost/Reports. 2. Click the Home link at the top of the page, click the Adventure Works Samples folder link, click the Actual Vs Quota report link, and then click the Properties tab. 3. Click the Security link. 4. Click Edit Item Security, and then click OK to confirm the folder setting changed from its parent s setting. 5. Select the AWSalesAnalyst and the AWSalesDirector check boxes, and then click Delete.

Part III: