fix: [UIE-10093], [UIE-10139] - IAM Users Table: Fix pagination when the last user on a page is removed, UX copy updates

[mpolotsk-akamai]

Description 📝

This PR fixes pagination in Users Table when the last user on a page is removed.

Changes 🔄

List any change(s) relevant to the reviewer.

• Navigate to the previous page to avoid showing an empty table
• Fixed empty table styling issue
• UX copy updates

Scope 🚢

Upon production release, changes in this PR will be visible to:

• All customers
• Some customers (e.g. in Beta or Limited Availability)
• No customers / Not applicable

Preview 📷

Before	After
Screen.Recording.2026-02-02.at.11.54.09.AM.mov	Screen.Recording.2026-02-02.at.11.52.20.AM.mov

How to test 🧪

Prerequisites

(How to setup test environment)

• use IAM Parent/Child account with mock data

Verification steps

(How to verify changes)

• Go to /iam/users with 26 (or more) users.
• Go to the last page of the table.
• Click "Delete User" from the User Actions menu and delete one or more users until the last page becomes empty.
• Verify that the table navigates to the previous page.

Author Checklists

As an Author, to speed up the review process, I considered 🤔

👀 Doing a self review
❔ Our contribution guidelines
🤏 Splitting feature into small PRs
➕ Adding a changeset
🧪 Providing/improving test coverage
🔐 Removing all sensitive information from the code and PR description
🚩 Using a feature flag to protect the release
👣 Providing comprehensive reproduction steps
📑 Providing or updating our documentation
🕛 Scheduling a pair reviewing session
📱 Providing mobile support
♿ Providing accessibility support

• I have read and considered all applicable items listed above.

As an Author, before moving this PR from Draft to Open, I confirmed ✅

• All tests and CI checks are passing
• TypeScript compilation succeeded without errors
• Code passes all linting rules

[abailly-akamai]

@mpolotsk-akamai can you see if #13346 fixes your use case as well?

[aaleksee-akamai]

@mpolotsk-akamai can you see if #13346 fixes your use case as well?

@abailly-akamai but here is server-side pagination, and the table wasn’t updated after the data changed. So something is off with it

[mpolotsk-akamai]

@mpolotsk-akamai can you see if #13346 fixes your use case as well?

@abailly-akamai , this change doesn’t fix my case.

[linode-gh-bot]

Cloud Manager UI test results

🔺 1 failing test on test run #3 ↗︎

❌ Failing	✅ Passing	↪️ Skipped	🕐 Duration
1 Failing	864 Passing	11 Skipped	37m 24s

Details

Failing Tests
	Spec	Test
❌	clone-linode.spec.ts	Cloud Manager Cypress Tests→clone linode » can clone a Linode from Linode details page

Troubleshooting

Use this command to re-run the failing tests:

pnpm cy:run -s "cypress/e2e/core/linodes/clone-linode.spec.ts"

[abailly-akamai]

@aaleksee-akamai @mpolotsk-akamai yes, sorry we are dealing with server side pagination.

I find it surprising to have to do this. I wonder if this is always the case or if this is isolated with this particular case. Cause we would also want to try to fix it as the hook level if this is a general problem

[abailly-akamai]

The fix works - perhaps we can work on a more holistic solution in the future. Those are still edge case so it's not a big priority to spend much time on it. thx!

[aaleksee-akamai]

if I remember correctly, @abailly-akamai is not a big fan of passing down boolean props, and we had this discussion when I implemented that logic for this table