Topic Status: Some information in this topic is preview and subject to change in future releases. Preview information describes new features or changes to existing features in Microsoft SQL Server 2016 Community Technology Preview 2 (CTP2).
If default security settings do not provide the level of access that you require, you can create new permission levels to provide access to specific report server items or operations. Custom security settings can be useful if you want to restrict access to a particular report.
You must be a site owner to create permission levels and groups. Permission levels are used globally throughout a site. If you create a new permission level, it will be available to other site owners.
Most permissions are inherited from a parent site. If you assign permissions on a specific library or item, you break permission inheritance and incur additional overhead in how manage permissions for that branch of your site hierarchy.
You can set permissions on report definition (.rdl), model (.smdl), and shared data source (.rsds) files. You cannot combine inherited and managed permissions on the same item. If you choose to manage permissions directly, inherited permissions will have no effect on the current item. If you want to resume permission inheritance later, you can select Inherit Permissions on the Actions menu.
To set permissions on entities and perspectives in a model, you must have Full Control level of permission for the model. Full Control includes "Manage Permissions", which is a site level permission that is granted to site owners and other SharePoint groups who have Full Control level of permission. If you want to offer specific users the ability to set model item security, you must break permission inheritance and grant elevated permissions (such as Full Control) to the user or group on the model file. When you grant Full Control on an item such as a file in the library, the permissions are scoped to that item and do not extend to the parent or to other items within the same library. After the user has Manage Permissions permission on the model, he or she can use set model item security via the SharePoint site or Model Designer.
To set permissions on an individual report, model, or data source
If the library is not already open, click its name on the Quick Launch. If the name of your library does not appear, click View All Site Content, and then click the name of your library.
Point to the report, report model, or shared data source file.
Click the down arrow, and on the menu, click Manage Permissions.
On the Actions menu, click Edit Permissions, and then click OK to confirm the action.
To give permissions to a user or group that does not yet have permissions to use the file, click New, and then click Add Users.
To remove or modify permissions for an existing user or group, click the check box next to the user or group, click Actions, and then click Remove User Permissions or Edit User Permissions.
To set permissions that enable model item security
Log in to the SharePoint site using an account that has Manage Permissions permission on the site.
Open the library that contains the model.
Point to the model.
Click the down arrow next to the model, and click Manage Permissions.
Click Edit Permissions. Click OK.
Click Add Users.
In Users/Groups, enter the user account.
Select Give users permission directly.
Click Full Control.
Click OK. Once a user has the ability to manage permissions for a specific model, he or she can open the model to edit permissions within the model.