How to Create Role Assignments with SQL Server Reporting Services - dummies

How to Create Role Assignments with SQL Server Reporting Services

By Mark Robinson

Part of Microsoft SQL Server 2005 Reporting Services For Dummies Cheat Sheet

SQL Server 2005 Reporting Services includes several predefined roles to accommodate various categories of users. You can see the roles defined in SQL Server Management Studio when you expand the Roles folder within the Security folder in the Report Server.

If you right-click one of these roles and choose Properties from the list that appears, you’ll see the detail task permissions checked for that role.

You can create additional roles if the predefined roles are insufficient. You can modify or delete either the predefined roles or the custom roles you create, as long as you don’t invalidate the last remaining role assignment for your report server. You can define a new role or edit an existing role within Report Manager of the SQL Server Management Studio.

To create a role assignment in Report Manager, proceed as follows:

  1. Navigate to the Contents page, and open the folder that contains the item for which you want to apply a role assignment.

  2. Click the Properties tab, then click the Security tab, and perform one of the following:

    a. If the item uses the security settings of a parent item, click Edit Item Security, click OK, and then click New Role Assignment.

    b. If the item already has item-specific security defined for it, click New Role Assignment.

  3. Type the name of a group or user account.

    You can specify only one account name for each role assignment.

  4. Select one or more role definitions that describe how the user or group should access the item, and then click OK.

  5. To determine which tasks a role definition supports, click the name of the role definition.

  6. If existing role definitions are insufficient, click New Role to create a new one.

Role definitions can contain either item-level or system-level tasks. You cannot combine tasks from both levels into a single role definition. Because the number of tasks that you can work with is relatively small, you typically don’t need a large number of role definitions. Creating or modifying a role definition requires careful consideration. If you create too many roles, the roles become difficult to maintain and manage.