We’ve updated the user experience for administrators by bringing Identity Profiles in alignment with our modernized design.
We have improved and modernized the user experience for Identity Profiles administration, including improving usability, refreshing the design, hastening load times, and increasing accessibility. The core functionality has not changed - but the user interface has been renovated!
@NataliaYunusov please, for the love of all that is good, stop removing the nav bar. In addition to being essential for navigability, the nav bar also serves as an important indicator of which environment we’re working in - many customers use a different color for the nav bar between their sandbox and production environments to more easily distinguish between the two. But it’s really the loss of functionality with regards to navigation that’s frustrating here.
Please see https://ideas.sailpoint.com/ideas/GOV-I-3653 on the Ideas Portal. This has already been raised as a pain point over a year ago, and acknowledged with a Future Consideration status, so it’s frustrating to see that this complaint is being fully ignored and this is spreading rather than being fixed.
When a new UI update is coming we always have to get used to it and could complain about the new look. But to enforce on what @sup3rmark wrote above, not seeing the navigation bar is a big step back.
Identity Profiles updates are not BAU but occurs often when pushing a config from the Sandbox to Production. Doing that through the Configuration Hub get tricky as the attribute and source references are not identical (the object mapping is not solving all issue). Then we end up with two sessions opened on the identity profiles comparing both environments, each having its own branding color (best practices is so set different logo and color for each environment).
With this UI change, we cannot identify easily which session belongs to the source and which one to the target environment and is prone for errors.
Great update but please, do not mask the navigation bar!!!
While I understand the intent behind modernizing the interface, it’s unacceptable that a core action like saving changes within Admin → Identity Management → Identity Profile → Mapping is currently broken. After updating or deleting a row, the Save button simply does not respond. Attempting to leave the page triggers a warning about unsaved changes, yet there’s no way to actually commit them.
This is a critical workflow, and right now it’s non-functional. Please prioritize fixing this — it’s blocking real work. The only alternative now is to use API/VSCode.
Thanks for raising this. We’ve tested the new experience and have consistently been able to modify and save changes without issue. That said, it’s possible there’s an edge case we’re not hitting. If you’re able to share more specific steps or conditions that led to the unresponsive Save button, it would be really helpful.
Regarding the unsaved changes modal, this is expected behavior if changes haven’t been saved. We are aware of one scenario where the modal appears even when no actual changes were made. A fix for this is already in progress and will be pushed to Staging ASAP.
Thanks, everyone, for the feedback on the missing navigation bar. Really appreciate you taking the time to call this out.
I brought this up with our UX team, and the current approach is intentional. For pages in a “takeover” experience like identity profiles, roles, access profiles, and sources, the nav bar is removed to help keep the user focused on the specific object they’re working on. The idea is to complete the task or action, then close the takeover to return to the broader list view.
That said, I completely hear your concerns around usability, especially for multi-tab workflows and environment differentiation. I’ve passed this feedback along to the team and will keep you posted if we make any changes here. Please continue upvoting the idea in Aha if this is important to you.
Thanks for the clarification, Natalia. As a long-time IDN/ISC user (8+ years, 4 implementations as a customer and 12+ as a SailPoint Partner), I can tell you that this is simply not how we work. Forcing users to “focus on the specific object they’re working on” is not something we need the application to do for us. We’re grown-ups, if loss-of-focus is an issue, let that be our issue, not yours. It’s significantly more important to have the nav bar for the dev vs prod identification and for the general navigation, because we often need to navigate away to another page to check something while we’re still in the middle of the current task. This anti-pattern is not even being applied consistently, with back/exit buttons applied on different sides of the screen - for example, if I’m drilled into a specific account, I have to first click < Accounts in the top left corner of the screen, then the X in the top right corner to get back to the Identities list. This new paradigm results in more unnecessary cursor movement and more clicks to accomplish the same thing versus the previous interface.
This was not broken, so it’s weird that this is the thing that has been determined needed changing. There are other UI/UX elements that are actively broken (like the annoying little light bulb button that covers pagination buttons on the Search results page) that should be fixed instead. Granted, there was a scaling bug with the current Identity Profile lifecycle state mapping page, but surely that had nothing to do with the nav bar…
Yeah bring the nav back. ISC requires you to have multiple tabs open to troubleshoot and compare things, so make life a little easier for us. Simple as that.
Please don’t take away the nav bar, and stop forcing users to “focused on the specific object they’re working on”. I can focus just fine with the nav bar included.
To reiterate what others have said, hiding the navigation bar is not optimal for end users in my opinion. The rest of the changes to the page look fine though.
Have already escalated to our CSM to revert our tenant but the new Identity profile UI is un-usable and is impeding our work in our dev environment. It looks good but it does not work.
It takes at least 20 seconds to load the mapping screen and then when trying to change the source / attribute / transforms drop downs by typing it crashes/ lags again for 10 seconds. You can manually try scroll through but if you have 100+ attributes its impossible.
Completely unusable and verified similar symptoms with others on my team and Sailpoint Pro services
We understand how disruptive this is and want to assure you that we are actively investigating the issue today and will continue to do so. If we are unable to identify the root cause or fully understand how widespread the issue is, we will likely delay the production rollout to avoid further disruption.
If you have not already, please open a support ticket so we can properly track and investigate the root cause.
Thank you
I’ve tested this in my lab tenant, and it works as expected — I’m able to delete an empty mapping or update a mapping to an empty value without any issues to be more specific. However, the same actions are not possible in a production environment with an actual customer, which is quite unusual. Interestingly, the system does register the change, as evidenced by the message: “Are you sure you want to discard your work?”
Despite this, clicking “Save” does not produce any result. While we’ve managed to work around the issue using the API, I’m considering opening a support ticket to resolve it properly.
The Production rollout of the new Identity Profile UI is temporarily delayed while we work to resolve an outstanding performance issue on the Mappings page. We’ll provide a revised timeline as soon as the issue is addressed. Thanks for your patience!
The LCS numbers have gone haywire in my tenant upon this update. Its showing 0 identities under active LCS and only 8 terminated identities for auth source identity profile.
Please advise if this is a known issue and others have faced it too or if there is a fix in progress.
We are experiencing the same issues described by Paul Vu regarding the new Identity Profile UI in our Stage environment. It’s extremely slow—taking 20+ seconds to load mappings—and the dropdowns (for source, attribute, transforms) are laggy or unresponsive, especially with large attribute sets. Using Ctrl+F to find an attribute takes just as long. Save button also not working. This is seriously affecting our development work.
Please advise if there’s a way to revert or improve performance.
We’ve updated the user experience for administrators by bringing Identity Profiles in alignment with our modernized design.
