We are migrating from SSRS 2008 R2 integrated with SharePoint 2010 to SharePoint 2013/SQL Server 2012 SP1 backend. In our test migration, everything works great except that end users are now unable to create SSRS subscriptions. All end users in our current farm are in the Read permissions group, and can create/manage subscriptions both for themselves and others.
Turns out this is apparently an intentional design change on the part of the product team at MS.
We are kind of stuck, as we want our users (potentially anyone in a company of 850) to create/manage their own subscriptions and also at times create subscriptions that get emailed to other employees.
We are not too keen on giving our end users Edit Items permissions on all SharePoint libraries where they might just need to create an SSRS subscription. In addition, even with their permissions increased with "Edit Items", they are unable to create a subscription for someone else; as I said above a common need in our environment. This requires the additional site permission of "Manage Alerts", and would allow them to then see/modify all subscriptions, not just the ones they created.
So, we are looking for any guidance on possible workarounds or other ways to allow end-user self-service SSRS subscription management while minimizing (or ideally not allowing) other permissions.
Even if there was a way to get alerted to changes on report properties that would help. Unfortunately, all SSRS-specific "Manage" features available in the dropdown in the SharePoint library work completely outside SharePoint document management and alerting mechanisms - i.e. no alerts, no versioning, no check-out or content approval required for any of these "Manage..." changes.