Enhancement: Access Request Approvals layout update

Description

:bangbang: **We are pleased to announce that we’re updating the access request Approvals page user interface! **

We’re changing from tiled cards to full-page-width cards for improved visibility and usability.

What is the Problem?

The tiled-cards layout offered limited space for displaying names and descriptions, often creating inefficiency by requiring users to hover over the information to understand what they were being asked to approve.

What is the Solution?

The new layout stacks approval cards vertically so we can use the full page width to show each item’s full name and description and make it easier for reviewers to navigate through their approval items. Reviewers will still be able to click each card to see additional details when they need more information to make an informed decision.

Previously completed access request approvals still appear as a separate tab within the Access Requests approvals page, also updated to the new layout.

Important Dates

Our planned release schedule for this change is:

  • Sandbox tenants: Monday, May 20
  • Production tenant phased rollout:
    • Batch 1: Monday, May 27
    • Batch 2: Wednesday, May 29
    • Batch 3: Thursday, May 30

We’re excited about this usability improvement and look forward to hearing your feedback!

7 Likes

Hi @jennifer_mitchell,

Thank you for the announcement! I am looking forward to the change as I do think vertical tiling over matrix tiles are more user friendly and the fact that you can read the full names is also a big plus.

Some questions from my side:

  1. Will the end user be able to filter between the different types of access requests? (Grant, Remove, Prolong the end date, Shorten the end date)
  2. Currently, there is a coloured background for the words Grant or Remove. In the new version I only see the text followed by a colon. Since there is a big difference between adding access and revoking access, shouldn’t this keep a more prominent position in the UI layout? It almost looks as if the access item is now called “Grant: Sales Global Mainframe”. If access items have colons in their name, we would even see something like “Grant: Approve: Expense Request”
  3. Currently, any tile that has comments has a comments icon in it. How will this look like in the new version?
  4. How can we determine to which batch we belong for production deployment we belong?
  5. Since this touches end users (approvers), will there be a flow that informs the end users of the new UI and give some kind of tour?
  6. With the current release schedule, we only get a week between sandbox and production to ensure that we update our training material and inform our end users. Also we only get a week to explore this functionality and give our feedback/concerns on this. Wouldn’t it make sense to add some more time between sandbox and production releases?
  7. Currently we can see whether the access item is an entitlement, an access profile or a role. I don’t see this distinguishment in the new layout. Was this removed accidentally or on purpose?
  8. Will the requested date appear in the culture matching the approvers browser?
  9. Will it still be possible to click on the tiles to see the additional information like we can currently see?
  10. How does the “reviewed” page look like? I see a tile with a yellow warning icon on a reviewed tile in a tenant I use. Hovering on it or clicking on it does not give me additional info. Will this be changed in the new UI?
  11. With a matrix field you would need to scroll down a lot to see older tiles, but for one column of tiles it will be even more. Will this UI change include a way to filter on passed reviewed items? Perhaps by recipient, perhaps by date?
  12. Will there be a point in time where passed reviewed items disappear? If so, when will that occur?
  13. I see that next to the SailPoint logo (which is a different logo for tenants who use branding) it says MySailPoint instead of “Home” which I currently see in both sandbox, production and ambassador tenants. Will this get changed as well? I hope not, this update was already reverted earlier after SailPoint received feedback. See Update 3 here:

Kind regards,
Angelo Mekenkamp

1 Like

Lots of questions here @angelo_mekenkamp :laughing: ! The short answer is this is just a new appearance; functionality on this page is not changing with this update. But I’ll also address your list individually:

  1. The same filters we have today will be available, namely filter by access request and non-employee account request.
  2. That’s good input. We’ll see how feedback comes in about using this Word: instead of the badge.
  3. When comments exist, you’ll see a Menu where the “Reassign” appears in this screen shot which will include “Read Comments”. When there are policy violations, you’ll see Review Violations instead of Approve/Deny, and Read Comments will be shown next to it if they exist (in case comments explain the violation justification!).
  4. Batches: This is our normal production rollout process and is a grouping managed by our engineering team. I don’t know that you can determine which batch you are part of in advance.
  5. I will talk with the team that builds those in-app announcements/tours and see what we think is needed.
  6. Rollout schedule: This is our normal production rollout cadence. However, if we get a lot of feedback from customers concerned about this, we can revisit and slow this process.
  7. I hadn’t noticed that removal of the object type from the cards! I’ll circle back with the team on it.
  8. The requested date should appear the same as it does in the current cards.
  9. Yes, you will be able to click the card and see the full details just like today.
  10. The Reviewed page will be the wide card layout with no functional changes. I am not sure what you mean about the warning icon and not being able to click it - perhaps it was one with a policy violation (the typical reason for that icon). If it’s not clickable today, we won’t be adding that with this update.
  11. This UI does not yet add any filter/search options that don’t yet exist. However, I would like to add more filters/search options in the future.
  12. Currently we do not delete/archive old approval items (just leave them on the Reviewed page. This is actually something I want to investigate further and consider doing (figuring out what the right retention period is and whether we need the older data accessible elsewhere). But that is not changing now.
  13. This is a screen shot from an admin user and an internal tenant. Please ignore that. It is not part of this update and should not change in your tenants.
2 Likes

Thank you for all the clear answers @jennifer_mitchell! This is really helpful! We see it in our sandbox environments now and it does look good in general.

Regarding point 8: I do notice that the requested date appears in a different style. Before it showed the date in digits only d/MM/yy, and now it is in the form MMM d, yyyy. So it is different than what you described.

If I update my browser settings and prefer Dutch over English, I get the following error:

image

I haven’t checked the other languages that SailPoint supports.

Please make sure that new UI changes are being tested in all supported languages.

Kind regards,
Angelo

1 Like

In addition, I just noticed that if you double click ‘approve’ on a tile, you actually approved the tile you wanted to approve, but also the tile that was below it, because one click was sufficient and the second tile immediately replaced the former tile.

Note that regular approvers who might expect a double click being necessary or regular approvers who accidentally double click (either on their mouse or mousepad or different) will now approve items they did not mean to approve.

Should this be considered a security risk?

Kind regards,
Angelo

3 Likes

Thank you. I will circle back with the team on that date issue.

1 Like

We will monitor for this feedback. As I recall, if you clicked approve on the tiled cards, the card would disappear and the next card would take its place too, so theoretically, this same risk existed in the old layout too.

1 Like