Thank you for this feedback, and to everyone who has voted on and commented on this idea. I want to emphasize that we hear you; the current "Login As" behavior is disruptive for some workflows, especially when you're actively assisting donors and fund advisors over the phone.
We want to be transparent about why this works differently than it did before. In the previous workflow, the CSuite backend and the Fund Advisor portal were entirely separate logins. So, when you proxied in as a Fund Advisor, it was as if you were logging into a different system, so your CSuite session wasn't affected.
With the new portal, all logins are unified under a single authentication system. This change was part of the broader transition from the legacy Fund Advisor portal to the unified Foundation Portal, which enabled support for multiple user types (donors, grantees, vendors, etc.) and laid the groundwork for features like Single Sign-On. As a result, when you use "Login As" now, you functionally become that user. There is also a security component to this behavior; because all sessions now flow through the same authentication system, maintaining two simultaneous sessions under different identities could be flagged as unauthorized access. There is currently no underlying architecture in place to support a true proxy experience, where you could view the portal as another user while maintaining your own active CSuite session.
We understand this is a step backward in some workflows, and we don't take that lightly, but I hope some additional context here helps explain the reasoning behind our current functionality. Building the proxy infrastructure needed to restore this capability is something we're aware of, but it would require meaningful architectural work and is not a quick fix. We will continue to keep this idea on our radar as we plan future development.
In the meantime, some clients have found it helpful to use the Sandbox environment (when synced) to proxy in as a user without disrupting their live session, or to use a separate browser for Login As. We know these are workarounds and not solutions, but we wanted to share them in case they help. Thank you all again for the feedback.
Thank you for this feedback, and to everyone who has voted on and commented on this idea. I want to emphasize that we hear you; the current "Login As" behavior is disruptive for some workflows, especially when you're actively assisting donors and fund advisors over the phone.
We want to be transparent about why this works differently than it did before. In the previous workflow, the CSuite backend and the Fund Advisor portal were entirely separate logins. So, when you proxied in as a Fund Advisor, it was as if you were logging into a different system, so your CSuite session wasn't affected.
With the new portal, all logins are unified under a single authentication system. This change was part of the broader transition from the legacy Fund Advisor portal to the unified Foundation Portal, which enabled support for multiple user types (donors, grantees, vendors, etc.) and laid the groundwork for features like Single Sign-On. As a result, when you use "Login As" now, you functionally become that user. There is also a security component to this behavior; because all sessions now flow through the same authentication system, maintaining two simultaneous sessions under different identities could be flagged as unauthorized access. There is currently no underlying architecture in place to support a true proxy experience, where you could view the portal as another user while maintaining your own active CSuite session.
We understand this is a step backward in some workflows, and we don't take that lightly, but I hope some additional context here helps explain the reasoning behind our current functionality. Building the proxy infrastructure needed to restore this capability is something we're aware of, but it would require meaningful architectural work and is not a quick fix. We will continue to keep this idea on our radar as we plan future development.
In the meantime, some clients have found it helpful to use the Sandbox environment (when synced) to proxy in as a user without disrupting their live session, or to use a separate browser for Login As. We know these are workarounds and not solutions, but we wanted to share them in case they help. Thank you all again for the feedback.