Portals¶
A branded place to put your documents and data¶
Instead of emailing documents around, publish a portal: pages your own users sign into to browse, filter and download what you generate for them — your logo, your colours, your domain.
What a portal is made of¶
Tables, charts, navigation and text, arranged on a canvas the same way you build a report.
Widget reference
Each page pulls from your data sources and takes parameters, so what a visitor sees is current and filtered to them.
A shared design carries the theme, layout and navigation across every page in the portal.
How it comes together¶
A design bundles a theme with the page layouts every page sits in — navigation, header, framing.
Each page gets a route, its own data sources and parameters, and a tree of widgets on the canvas.
You edit a draft; publishing makes that version the one your users see.
Read next¶
-
Page and portal state
Where a value lives and how long it lasts —
$params,$data,$vars,$portal.stateand$user, and how widgets pass values to each other. -
Portal Assistant
An assistant inside the designer that can read the portal you are building and create pages, widgets and data wiring from a description.
-
Branding
Put your own logo, colours and domain across the product, portals included.
-
Move a portal between workspaces
Export a portal from one workspace and import it into another.
Before you start
Portals surface documents produced by reports, so it helps to have at least one report template working first.