CC/BCC and comments section is missing in the SSRS subscription page

Question

Good Mornig,

there ist already a very related topic on msdn-forums from where it is no longer possible to post. Answered but unsolved.

We are using SQL Server 2019 with reporting services SSRS. As pointed out in the above mentioned forum, a user cannot edit the comment-field in subscriptions unless granted with the "manage all subscriptions" permission. The comment field ist used as message body in email subscriptions.

Standard users oviously cannot be granted this "manage all subscriptions" permission.

However a standard user can create an email subscription and an admin can complete the message body of the Email in the comment-field. This subscription fully works and the standard user stays owner of the subscription and is able to see (not to edit) the comment-field.

Only if the standard user is trying to edit a field which he was originally permitted so edit (e.g. recipient-list), SSRS shows an error:

This eventually renders the subscription unchangeable for ist owner, the standard user. Could we possibly mark this behaviour as a bug and permit users to edit the comment field of their own subscriptions?

Regards, Christian

Answer 1

Hi @Christian Eschenburg ,
What are the roles assigned by standard users?
As far as I know, "cc", "bcc" and "reply" recipients seem to be only available when you are in the role of "manage all subscriptions", like the Content Manager mentioned in your link.
About enabling the "To" field, find <SendEmailToUserAlias> True </ SendEmailToUserAlias> in the rsreportserver.config file. By setting this to "False", users will be able to edit this field. The intention of this setting is to allow the user to add their email address when the SMTP server uses email accounts that are different from the domain user accounts. By allowing users to edit the field we can add as many recipients as we like, delimited by a semicolon.
Hope this helps.
Best Regards,
Joy

---

If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Hi @Joyzhao-MSFT ,

great to hear from you.

Our Standard User has the Browser Role plus "manage single subscriptions" permission. Hope my translation from German is correct. The Standard User cannot have the "manage all subscriptions" permission. This would be as if using a one-for-all user account.

The "To" Field has been editable for the Standard User from the beginnig. No Problem here.

However, we utterly need the Comment-Field, which is either not to be edited by the Standard User or renders the Subscription unchangeable if edited by admin in a second step. Please view red rectangle in the following Screenshot from related topic on msdn-forums.

Regards, Christian

Answer 3

Hi @Christian Eschenburg ，
If it is for report protection, I think it is possible to create linked reports, and then assign the "Content Manager" role for the specified linked report or the folder where the linked report is located. If you assign a role for the folder where the linked report is located, it is convenient to manage the subscription of multiple reports.

You could also try to create a role other than the five predefined roles in the report server and configure custom permissions.

I recommend that you use the linked report method and put the linked report in a separate folder, and then assign the Content Manager role to these users.
Best Regards,
Joy

---

If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 4

Hi @Joyzhao-MSFT ,

great news from you.

To use linked reports seems to be a workaround for us. Thank you!

We already work with linked reports to distribute reports into 30 different companies in the group. To create another linked report with individual permissions for every subscription seems to be not quite the solution yet. A lot of not schedulable administrative work lurking.

What is the protectional aspect in being able to create email-subscriptions only without email body? A lot of empty automated emails rather much lead to confusion here.

Regards, Christian

Answer 5

Hello @Joyzhao-MSFT ,

Is there any dev effort to address this bug? Although the linked reports approach addresses the issue, the underlying issue still persists.