Working with Report Manager - Learning SQL Server Reporting Services 2012 - page 184

Reporting Services, as we have seen in previous chapters, is a Windows service and so
it depends on Windows user authentication and does not store its own usernames and
passwords. However, Windows users must have permissions to access objects on the
Report Server. These permissions are set up on the Reporting Services and managed
by the Report Manager in the Security tab of most objects. The next section deals with
permissions and only a few of the many scenarios possible are explored with the
hands-on. However, these basic hands-on could be used for most of the usual cases.
Permissions in Reporting Services can be very fine grained and permissions can be set
for individual report if needed.
The available permissions were shown in Chapter 3 , Overview of SQL Server Reporting
Services 2012 Architecture, Features, and Tools , and you can find them on the Report
Server database in the Security node.
An administrator can set up new Item Roles , new System Roles and customize
them as in the link http://msdn.microsoft.com/en-us/library/ms186541.aspx .
For example, in SSMS, by right-clicking on the Roles folder in the Security
node, you can bring up a New Role... or Delete Roles (shown in the following
screenshot) window. By clicking on the drop-down item New Role… you begin
creating a new role.
Configuring role-based security
In the following you will be creating a few Windows users and assign them to Item
and System roles. We will use the ideas discussed earlier in assigning roles. We will
also create permissions to a specific item on the Report Manager.