Skip to content

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, under your logo, your colors and your domain.

Portal Designer Build one with AI

What a portal is made of

Pages and widgets
Tables, charts, navigation and text, arranged on a canvas the same way you build a report.
Widget reference
Live data
Each page pulls from your data sources and takes parameters, so what a visitor sees is current and filtered to them.
Your brand
A shared design carries the theme, layout and navigation across every page in the portal.
Portal themes

Before you start

Portals surface documents produced by reports, so it helps to have at least one report template working first.

How it comes together

1Design the shell
A design bundles a theme with the page layouts every page sits in: navigation, header, framing.
2Add pages and wire data
Each page gets a route, its own data sources and parameters, and a tree of widgets on the canvas.
3Publish
You edit a draft; publishing makes that version the one your users see.

Start from an existing portal

To build a portal that is close to one you already have, select it in the Portals list and click Duplicate (also available from the row's right-click menu). You get a new, unpublished portal named … (copy) with its own code. It includes every page, window and module, along with each page's data sources and parameters. It stays on the same design. Changes to the copy never affect the original.

Designs work the same way: Duplicate in the Portal Designs list gives you a new, unpublished design named … (copy) with every page layout and its data sources and parameters, using the same theme. Portals keep using the original design until you switch them.

Working on the canvas

Both the portal editor and the design editor draw the page in a device frame, with the widget library in the ribbon above and the properties panel on the right. You select a widget, drag it to size, and set its options on the right. Buttons don't run their actions on the canvas, so use the portal preview to click through windows and page links. The Portal Designer section walks through both editors.

  • Portal Designer


    The two editors: designs with their layouts, and portals with their pages, windows and versions.

    Portal Designer

  • Page and portal state


    Where a value lives and how long it lasts: $params, $data, $vars, $portal.state and $user, and how widgets pass values to each other.

    Page and Portal State

  • Actions and windows


    Buttons that open dialogs and drawers, move between pages with values filled in, and show notifications.

    Actions and Windows

  • Themes


    Colors, fonts, component looks, variants and reusable CSS overrides, shared by every portal on a design.

    Portal Themes

  • Access control


    Who can view, edit and manage each portal, and what people with less access see.

    Portal Access Control

  • 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.

    Portal Assistant

  • Branding


    Put your own logo, colors and domain across the product, portals included.

    White Label

  • Move a portal between workspaces


    Export a portal from one workspace and import it into another.

    Data Export · Data Import