Portal Pages
A Portal Page is a custom UI screen built for a Portal. Pages are the primary building block of a portal’s content - they can be linked directly from a Navigation item, making them accessible to users from the portal’s sidebar menu.
Portal Pages and Portal Components are built with the same editor and the same AI-driven workflow. The key distinction: a Page is a full screen referencable as a navigation destination, while a Component is a reusable UI element intended to be embedded inside pages or other components.
The Portal Pages screen
Section titled “The Portal Pages screen”Navigate to User Interface - Portal Pages to see all pages in the current application:
| Column | Description |
|---|---|
| Page Name | Human-readable name |
| Module Name | Which module the page belongs to |
| Created By | The user who created it |
| Modified On | Last modification timestamp |
Use + Add to create a new page, and the row checkboxes plus Delete to remove pages in bulk.
The AI Designer
Section titled “The AI Designer”Portal Pages are built in the AI Designer - a split-screen interface where a live preview fills the left panel and the AI chat occupies the right.
Describe what you want the page to do in the chat input (“Describe the UI component you want to build or refine.”) and the AI generates or updates the page. The preview on the left reflects the result immediately so you can evaluate the output before saving.
Context
Section titled “Context”The AI Designer knows about the platform’s UI primitives automatically. To make it aware of your data model - so it can generate forms that save to an entity, lists that read from a view, or actions that call a function - add items to its context using the + button next to Context in the AI Designer header.
Each added item appears in the Context list (e.g. “Entities: Invoice”) with a × to remove it. Click the Context (N) link to see all current items and a Clear all option.
File attachments
Section titled “File attachments”The paperclip icon next to + lets you attach files alongside your message - HTML examples, plain-text instructions, or screenshots. Attached files give the AI concrete reference material to work from, which is useful when you want the output to match an existing design or follow specific layout instructions.
Widget Settings
Section titled “Widget Settings”The Settings button (top right of the editor) opens the Widget Settings panel, where you can edit the metadata for the current page or component:
| Field | Description |
|---|---|
| UI Element Type | Page or Component - switching this converts the current item between types |
| Page Name / Component Name | Human-readable name |
| Page ID / Component ID | Auto-generated identifier |
| Application Module | Which module this page or component belongs to |
| Description | Optional free text |
The type toggle is the key feature here: a Page can be converted to a Component and vice versa at any time from this panel.
Where portal pages go from here
Section titled “Where portal pages go from here”A Portal Page becomes part of the portal’s experience by being linked from a Navigation item. It can also embed Portal Components to reuse UI logic built separately.