This is a critical, must-have functionality for database administrators and managers. Administrators need the ability to see Raiser's Edge through the eyes of their users, not just through their own access level. I am currently testing Prospect Insight Pro to understand how different user roles affect what people can see throughout the system. Since I do not have a portfolio myself, my test user account contains only three people in its portfolio. This is not sufficient to accurately test how portfolio information appears in different areas of the system or how the experience varies for users with different responsibilities and access levels.

Without the ability to impersonate specific users, administrators are essentially expected to configure, test, and troubleshoot functionality without being able to fully replicate the experience of the people using it. This creates a significant gap in our ability to validate changes before rolling them out. When users encounter unexpected behavior, they may report that a feature or the system itself does not work, when the actual issue may be related to their access, configuration, or the way the feature behaves for their particular role. We cannot reliably identify the cause or determine whether there is a genuine system issue if we cannot reproduce the user's experience.

Administrators should not have to rely on guesswork, incomplete test accounts, or repeated back-and-forth with staff to verify that the system is working as intended. The ability to securely impersonate a user would allow us to proactively test functionality, confirm what information is visible, troubleshoot reported issues accurately, and resolve problems before they affect productivity or erode user confidence in the system.

Portfolio visibility in Prospect Insight Pro is just one example of why this capability is necessary. This need extends across Raiser's Edge, wherever functionality, data visibility, and user experience vary by role. User impersonation would provide administrators with a practical and reliable way to validate the system from the user's perspective, improve support, reduce troubleshooting time, and ensure that new features and configuration changes work as expected for the people who depend on them. This should be considered a core administrative capability, not simply a convenience.

Just today I was working with a new employee. I saw when they logged in that they had access to a certain area that employees of his type should not have access to. Now I need to go back and see why he has access to that area. Instead of having to create a user just to test permissions, it would be nice to be able to "impersonate" the user I am testing things for.

Sometimes I have a user who either can do something they shouldn't be doing, or cannot do something they should be able to do, and it can be SO hard to get to the bottom of things when we have to rely on going back and forth with the user. It would be so much easier if admin/supervisor users could easily see this info.

This would eliminate a lot of extra work when users say they cannot access functionality.

Agree with all the above. With regard to bullet 1, I know I have the option to 'Update existing layout with additional tiles' for user home pages but sometimes I only want to update the 'Quick links' and not the tiles. Unfortunately that is not an option at this time. Right now I have to replace the home page layout which is the only way to get quick links to update and therefore it resets the way a user has their tiles set up (e.g. appeals they select, events they selected, funds they selected, etc...)

This feature would be immensely helpful! I am currently messaging Support and a user separately to try to remedy a permissions issue. The user needs to log off, and so now my work with Support has to be put on hold until the user can log back in and test for us again. If this feature were available, I would not need to keep asking the user repeatedly, "Does it work now?"

This feature would be beneficial to Admins for sure! A user I gave access to said he could not see all the tabs across the dashboard, even after I made additional changes (which I thought were needed) to resolve the problem. I had him send me a screenshot of his page and I searched online for causes, and it turned out that his screen was made smaller so the tabs collapsed under a drop list. So if I was able to "impersonate" the user, I would have known the role setup was correct and the issue was unique to him and his page setting.

This would so great and important to have! I just recently went through having to work with ITS to create a test account which was not easy. Agree with all of Jen's points!

I second everything Jen laid out. We shouldn't have to create test accounts using a different email address just so we can see what the end user (i.e. staff member) sees. The ability to quickly see what the end user sees would definitely simplify what is already a complex job as an admin person for this database where I'm managing 50+ users at any given time.

This would be awesome. Great Idea!

Jen has laid out an incredibly compelling case for this improvement! We are very much lacking in data admin tools in webview and this would be a huge help. I agree with her 100% on all points and hope that Blackbaud will seriously consider this change.