We would like to have a possibility for users without Edit Security or Audit permissions to fetch user management data.
Meaning just read the data, should not be able to modify anything.
One simple Use case: Sending Email notifications from ${release.owner}'s email id instead of prefilling the FROM field on the template.
${release.owner} is always userId, and there is no possibility to fetch emailId linked to userId.
Above mentioned Usecase is one of the simple use cases, but there are more use cases where fetching atleast the emailId makes sense.
by: Sanjay M. | about a month ago | Permissions
Comments
Thank you for the idea. You mentioned this is one of the simpler use cases, and that there are others where access to user data - like email addresses - would be useful. To evaluate this properly, it would be helpful to understand a few of those additional scenarios.
Are there other roles where you're sending emails or using user information dynamically? If so, which ones?
Having that context will help us determine what kind of improvement would be most valuable also to the broader customer base.
One other use case would be to pickup the task assignee and use his/ her email ID to send out emails.
Also, same holds good for MS Teams notifications, the message should go from either the release owner or the task assignee name instead of a pre-filled name.
Apart from use cases relating to communication (Email and MS teams), we have not seen other use cases yet.