Are we able to see the configuration of a users notifications settings without having to impersonate them to do so?
There are some settings you can see in their account profile info in the back office dashboard but they're not the individual notification settings.
Am I just not looking in the right place or is it not something we can do without impersonating the user and looking there?
Thanks Tom Paolucci Just wanted to make sure I wasn't missing something before we add another idea to the list.
Checking someone's notification settings is really useful if they tell you that they're not receiving them. Yes I guess we can impersonate them but that feels a bit weird to have to do that rather than just checking in their account info as an admin.
I'm not sure if it works in the same way but in our previous platform, if you impersonated an account you were 'logging them in' . This then could cause other actions/automations or account info updates to run based upon the CRM info sync and potentially send out notifications and emails to them which (as they were not expecting them and hadn't logged in themselves) would cause them alarm. As you can imagine, this resulted in many an urgent email/call to us saying that they believed their account had been hacked... 
We then had to come up with a process of only impersonating a user for specific reasons and always with the consent of the user so they were aware if it made changes to their account info and trigged any emails.
So as you can see, we try not to impersonate a user unless we really need to so it would be great to be able to see and adjust their notification settings in their standard account info. 
I hear you Tom! 
Yes it's a great option to have and can be incredibly useful in certain circumstances BUT we felt that we needed to have some form of process/policy around when it is appropriate to impersonate a user and for what reasons. In our previous community Admins could not impersonate other admins but I believe Verint community allows that? It's good that it records the action of impersonating in the auditing though so you can see exactly who has done what! 
I hear you Tom! Yes it's a great option to have and can be incredibly useful in certain circumstances BUT we felt that we needed to have some form of process/policy around when it is appropriate to impersonate a user and for what reasons. In our previous community Admins could not impersonate other admins but I believe Verint community allows that? It's good that it records the action of impersonating in the auditing though so you can see exactly who has done what!
