Navigation: deep links bounce, so no admin URL is addressable

[lonelycode]

F1 — Deep links bounce (escalate this one)

Hard-navigating to /admin/filters/new lands on /admin/apps/1. /portal/dashboard from an admin session lands back on the last admin route. Every navigation in every demo is a click, because URLs are not addressable.

This means an admin cannot:

• bookmark a page
• share a link to an object in a ticket
• deep-link from an email or an alert
• reload the page they are on

It is invisible in a demo and infuriating in daily use. This is the highest-value item in this issue.

F2 — The admin session expires briskly with no warning

Bounces to /login mid-task; any unsaved form is lost.

Fix: warn before expiry, offer renewal, and preserve the intended route so login returns the user where they were (which also depends on F1).

F3 — Ambiguous nav labels

LLM providers, Data sources and Tools each appear twice in the admin sidebar (once under management, once under Catalogs), and again in the portal sidebar. The Administration tab contains a collapsible section literally called AI Portal, which is also the name of a sibling top tab.

Measured cost: getByRole('button', {name: 'AI Portal'}) matches the tab and the sidebar section, and bounced a probe into the wrong tab twice. A human makes the same mistake with the mouse.

Fix: disambiguate the Catalogs children (LLM provider catalogs), and rename the Administration-side AI Portal section (Portal administration).

F4 — Collapsed sidebar sections unmount their children

So nothing on the page and nothing in the DOM tells a user where a screen lives until they open the right section by guesswork. The public docs' nav names don't match the app's tree either, so search doesn't rescue them.

F5 — Route inconsistency

ui/admin-frontend/src/admin/routes.js:188-195

catalogs/llms      catalogs/llms/:id      catalogs/llms/edit/:id      catalogs/llms/new
catalogs/data      catalogs/data/:id      catalogs/data/edit/:id      catalogs/data/new
catalogs/tools     ...

llms and tools are plural nouns matching their resource; data is neither datasources nor consistent with them. Cost a session's worth of wrong-path debugging.

Fix: catalogs/datasources, with a redirect from catalogs/data.

---

Acceptance

• Every admin and portal route is directly addressable, bookmarkable and reloadable
• Session expiry warns, and login returns the user to the route they asked for
• No two nav items share an accessible name
• Sidebar structure is discoverable without opening every section
• Catalog routes are consistent, with redirects from the old paths

From the UX & UI review of the demo set (section F).

[probelabs]

Thank You for This Detailed UI/UX Feedback

Hi @lonelycode. Thank you for taking the time to provide this incredibly detailed and well-structured report on the navigation and session management issues. The five points you've raised (F1-F5) clearly identify some significant pain points for daily use, and the context you've provided is invaluable.

Based on your report, I understand the key problems are:

1. Broken Deep Linking: Direct navigation to any URL results in a redirect, making it impossible to bookmark pages, share links, or reload. This is the most critical issue.
2. Abrupt Session Expiry: Sessions end without warning, leading to lost work and a jarring user experience.
3. Ambiguous Navigation Labels: Several labels are duplicated across different sections of the UI, causing confusion.
4. Poor Sidebar Discoverability: Collapsed sidebar sections unmount their children, hiding the navigation structure.
5. Inconsistent Route Naming: The route for data source catalogs (/catalogs/data) is inconsistent with other pluralized resource routes (/catalogs/llms).

These issues point to foundational areas in the frontend application, specifically routing, state management, and component design. The react-router-dom library appears to be central to the routing implementation, and the redirect behavior on deep links (F1) may stem from how application state is initialized or how protected routes are configured.

Next Steps

The engineering team will need to investigate the root cause of the redirect behavior. While your report is very clear, a little more information could help accelerate the debugging process for F1:

• Could you confirm if the deep link bounce happens even when you have an active, non-expired session? For instance, if you sign in, navigate to a page, and then try to reload that page or paste its URL into a new tab.
• Are there any errors or messages in the browser's developer console when the redirect occurs?

Your suggestions for fixes are clear and actionable. This report provides a strong basis for improving the core usability of the application.

References

• ui/admin-frontend/src/admin/routes.js – Location of the frontend route definitions mentioned in F5.
• ui/admin-frontend/src/App.js – The main application component where the router is likely configured, relevant to F1.
• ui/admin-frontend/src/admin/components/Sidebar/index.js – The component responsible for rendering the navigation sidebar, relevant to F3 and F4.

---

Powered by Visor from Probelabs

💡 TIP: You can chat with Visor using /visor ask <your question>