Thanks for reaching out on the Redgate forums regarding your SQL Monitor query.
Certainly, there are some details which you can check regarding redacted details of execution plans.
In UserPermissionsMapper.cs there is a line - "Permissions.QueryPlans.CanViewParameters" for admin permissions. If you have an admin role in SQL Monitor then they should be able to see them.
Depending on what authentication type (BASIC, AD, OIDC) you are using there is another check you can do.
SELECT * FROM settings.AuthPrincipals AS ap
Hope this helps track down the settings to alter the behaviour in your Monitor deployment
Apologies for the misdirection - the UserPermissionsMapper.cs file is in our code and not accessible/modifiable for end-users.
This has been escalated within our technical support team and we have found permission under the admin user level for being able to view the parameters but were unable to see how that linked up with the area in the software actually doing the redaction. We are escalating to the developers and will update this post when we have more information from the team.
It may be worth checking to see if you can add a login explicitly as a user and admin and see if they can then view the parameters.
If they can and if so, we can have a look at the priority for privilege based on different groups perhaps. If it doesn't work even when they are explicitly added, then something else is occurring which we will need to investigate further into.
Tips and how-to guides for Redgate products
Ask, discuss, and solve questions about Redgate's tools
Meet us at an event, get sponsored, and join our Friends of Redgate
In-depth articles and opinion from Redgate's technical journal