Portal copy and state: no pending state on a new App, wrong descriptions, dead buttons

[lonelycode]

Small, cheap defects where the product says something that isn't so. Several are one-word changes.

C1 — There is no pending state anywhere in the portal

A portal-created App's credential is minted inactive; an admin must press Approve this App before the key works. The portal says "submitted for approval" — accurate — and then shows the developer an App with a secret they can copy, with nothing anywhere indicating it is not yet live.

They discover it as a 401.

Fix: show the pending state on the App, grey the credential, and say what is being waited on. Two-line change, large support-ticket payoff.

C5 — "No description available" printed under tools that have a description

ui/admin-frontend/src/portal/components/AppDetailView.js:1155

{tool.attributes.short_description || tool.attributes.description || "No description available"}

Renders the fallback in the App page's Tool Access Details even when the Tool carries a description — the field being read is not the one being populated. Same pattern for datasources at :953.

C9 — Typo on a getting-started screen

ui/admin-frontend/src/admin/components/llms/LLMDetails.js:647

"…or have a default URL (for example Anthropic and OopenAI)"

C4a — View in Catalogue goes to the dashboard

On /portal/submissions/{id}, the one button that would close the loop for a contributor navigates to /portal/dashboard. Reproduced twice.

C8 — "PDF export" in Chat is window.print()

With an injected header — browser print-to-PDF, not server-side generation. Reword the control to match.

C10 — Edge "Remove Entry" is cosmetic

A still-running edge re-registers itself. Either implement a real deregister/revoke or say what the button does.

---

Acceptance

• Portal App shows a pending state with the credential visibly not-yet-live
• Tool/datasource descriptions render when present
• Typo fixed
• View in Catalogue navigates to the catalogue entry
• Chat export control names what it does
• Edge "Remove Entry" either works or explains itself

Note: C3 (Key ID rendering blank) was already fixed — AppDetailView.js:614 now reads key_id. From the UX & UI review of the demo set (section C).

[probelabs]

Hello @lonelycode,

Thank you for this incredibly detailed and well-structured report! We appreciate you taking the time to identify and document these UI/UX issues, complete with code references. This level of detail is extremely helpful for our team.

Based on your report, I understand there are several distinct issues related to the portal and admin UI:

• C1: Missing "Pending" State: New App credentials are inactive but appear live in the portal, causing confusion and 401 errors.
• C5: Incorrect Descriptions: Tool and datasource descriptions are not displayed correctly in the App detail view.
• C9: Typo: A typo ("OopenAI") exists on the LLM details screen.
• C4a: Broken "View in Catalogue" Link: The button on the submission detail page navigates to the dashboard instead of the correct catalogue entry.
• C8: Misleading "PDF export" Label: The chat export function uses the browser's print functionality, and the label should reflect that.
• C10: Ineffective "Remove Entry" for Edge: The button does not permanently remove an edge registration.

Your analysis seems correct, and these are all valid points that impact the user experience. The issue with the missing pending state (C1) is particularly important as it directly affects a key developer workflow. The other items are valuable polish that contributes to a better overall product.

The report is clear and provides all the necessary information for our team to investigate. No further clarification is needed at this time. The issue has been added to our backlog for review and prioritization.

References

• ui/admin-frontend/src/portal/components/AppDetailView.js – Referenced in C5 regarding missing descriptions.
• ui/admin-frontend/src/admin/components/llms/LLMDetails.js – Referenced in C9 regarding a typo.

---

Powered by Visor from Probelabs

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

[lonelycode]

Mostly addressed by #518 and #528 (both merged). One item outstanding — leaving open.

Done

• C1 — the portal now says when a credential is not live. The data was already there (CredentialDetail.active is serialised) and was rendered as a bare Active: Yes/No row that is easy to miss and explains nothing. There is now a notice naming what is being waited on and what happens if you use the key anyway (401), the credential block is greyed while pending, and the row is a status chip reading Pending approval.
• C9 — the OopenAI typo (fix: name people in the review history, and stop printing raw enums (#512, #513) #518).
• C8 — the Chat Export button opens window.print() with a header injected. It is browser print-to-PDF, not server-side generation, so it now reads Print with a tooltip saying where the PDF comes from. Applied to both the chat and agent-chat toolbars.
• C10 — this was better than reported: the Remove Entry dialog did explain itself. But it said the gateway "can re-register automatically if it reconnects", which is conditional phrasing for something certain, and never said the button neither deregisters nor revokes. Rewritten to say so plainly.

Already fixed before this programme started

• C3 (Key ID blank) — AppDetailView.js already reads key_id.
• C5 ("No description available" under tools) — the fallback chain already includes tool.attributes.description.

Both were verified rather than assumed; no change was needed.

Outstanding

• C4a — View in Catalogue navigates to /portal/dashboard. Real and reproduces, but not fixable in isolation: portal/routes.js has no route for a single tool or datasource (it only browses catalogues by catalogueId), and the dashboard is a 101-line landing page, not a catalogue browser. Pointing the button at a different wrong page would not be an improvement. Sequenced onto the navigation work in Navigation: deep links bounce, so no admin URL is addressable #514.