Wir verwenden Cookies
Wir verwenden Cookies und ähnliche Technologien, um Ihre Erfahrung zu verbessern, den Datenverkehr zu analysieren und Inhalte zu personalisieren. Sie können alle Cookies akzeptieren oder nicht wesentliche ablehnen.
A participant portal is a website you own: pages you write, a menu you lay out, your logo, your domain — with the signed-in part wired to your organization’s own data. This guide walks the Design step end to end: creating the portal, choosing a starting point, then each of the four panels on the left — Pages, Layouts, Components and Branding.
The listing you came from is the home of every portal you run: name, Status, Panel Domain, Version and Updated. You can run several portals side by side, each on its own domain.
A portal is served on a custom domain you own and have verified. You can build and preview without one, but publishing needs an active mapped domain. See Setting Up a Custom Domain for Your Participant Portal.
A brand-new portal opens the template chooser. There are two ways in.
Describe the portal in your own words — its purpose, the public and private pages you need, and the content — and the AI builds a full multi-page portal you can then refine. The most useful prompts name the split explicitly, e.g. “public pages for services, our team and online booking; and a private patient area to view appointments and track recovery progress”. Starter prompt chips sit under the box; Generate with AI runs it.
Six starters, filterable by category: Retailer Portal, Education Portal, Support Portal, Research Portal, Survey Analytics Portal and Blank Canvas. Each seeds pages, a layout with a working menu, and components wired to sensible data. Reopen the chooser any time from Templates in the Pages panel, or Change Template in the toolbar.
The editor is a three-step wizard — Design, Preview, Publish. Four icon tabs run down the left of the Design step; the canvas renders the page you are editing; a settings panel opens on the right when you select a component. Desktop and Mobile above the canvas switch its width.
The Pages panel lists every page with its layout chip, title and slug. New opens the page drawer; the row icons hide, edit, clone and delete.
| Field | What it does |
|---|---|
| Page Title | The page’s name — browser tab, menus, and the default search title. Translatable. |
| Slug | The URL path; lowercase letters, numbers, /, _, - and :. A slug with a colon segment — the hint shows orders/:orderId — is a dynamic page: one definition rendering a different record per URL. |
| Layout | Which layout wraps this page. None renders it bare. |
| Who can see this page | The three access levels, below. |
| Landing page | Makes this page answer /. See below. |
| Search appearance | On non-private pages only: search title, search description, share image, and a Hide from search engines switch. |
Three cards. The choice decides whether the page is exposed to the internet at all.
“Only signed-in participants. Not reachable by search engines.”
“Anyone on the internet, no sign-in. Server-rendered so search engines can index it.”
“Anyone can read it; signed-in participants see more. Appears in both menus.”
There is one landing page per class, not one per portal. On a private page the checkbox reads Default page after sign-in; on a public one, Default public page. Ticking one replaces the previous holder in that class only — so a marketing home page and a participant dashboard can both own /, each for its own audience.
A layout is the chrome around a page — header or sidebar, footer, and one Page Content injection point where the page’s components land. New asks for a Layout Name and a Layout Structure:
Most portals end up with two — a public one with a top bar and a private one with a sidebar. Pages pick their layout in the page drawer, so moving a page between them takes a moment.
There is no Navigation tab any more. The menu is a nav container you drop into a layout, and each entry is a real, selectable link inside it. Older portals were migrated automatically — open the layout and your menu is there.
Select the nav container and its settings offer two knobs:
| Knob | Values | Effect |
|---|---|---|
| Position | Normal · Sticky · Fixed | “Sticky keeps the bar visible on scroll.” |
| On mobile | Stack · Menu button · Scroll sideways | “Stack and Scroll sideways keep this menu on phones with its mobile styles. Menu button hands phones to the app shell (top bar + drawer + bottom tabs) and hides this menu.” |
On a page anonymous visitors can read, the server removes any menu link pointing at a private page — the label of a private page must not print on a crawlable page. The canvas tells you before it happens: such a link renders dimmed with a small lock, tooltipped “Hidden for visitors who aren’t signed in: this menu is on a public page, and links to private pages are removed there. Link to Sign In or a public page.” The link editor shows the same warning with a one-click Use Sign In button.
In the link editor choose Internal page and pick Sign In — it is offered alongside your pages, and private pages there carry a warning-coloured lock. It is the only app route a public menu may point at: a “Register” link works in the designer and the preview but is removed on the live public page, and the sign-in screen carries its own registration link anyway.
The Components panel is the palette. Drag a block onto the canvas or click to append it; everything you drop gets a settings panel on the right. Alongside the general text, media and design blocks — headings, paragraphs, images, buttons, links, sections, rows, the nav container, dividers and spacers — portals add their own group:
The injection point where a page’s components render. Every layout needs exactly one.
One aggregated number — count, average or sum over an entity, with an optional filter. Three in a section make a metrics row.
A paginated table with configurable columns, sort and row actions. Its Heading knob sets H2, H3 or hidden — the page owns the H1.
One record in full, read from a URL parameter.
The participant’s own submissions. Toggles for summary metrics, a survey filter, and the survey, score, pass/fail and status columns.
A summary card of best and average scores, and a history of past attempts.
The participant’s details, editable in place. Optional phone, bio and panel type.
Your analytics widgets in the participant’s own context.
The surveys assigned to this participant, as a card grid or a table, with editable start, retake and results buttons.
Published posts as a card grid or list, with sort, page size, pagination style and a Content Type.
One post in full: cover, title, body, date and tags, with a crawlable link back to the listing.
The list-plus-detail pattern is two pages and two components. Create a page with a dynamic slug such as orders/:orderId, drop a Data Detail on it, and point a Data List row action at that slug. The row’s record id lands in the URL and the detail component reads it.
Blogs work the same way, but by slug. Set the listing’s Post Detail Page to the detail page’s slug (say blog/:postId) and the detail block’s Post field to :postId. Posts then live at readable, crawlable addresses like /blog/post-surgical-shoulder-stiffness. Leave Post Detail Page blank and titles are not links and no post is crawlable.
The Branding panel is described as “Shown on login, register, and landing pages”, but the logo in particular is used throughout the portal.
The toolbar carries the rest. The Settings popover holds general settings, Language, Style, sharing, and — once a domain is mapped — Auto-approve sign-ups: “When off, new sign-ups wait for an admin’s approval before they can access this portal.”
Every text field follows the language shown in the toolbar as Editing in; add locales under Manage Languages and untranslated strings fall back to the default one. Edits save on their own, and Version History keeps every saved state — Compare one against the current draft, then Restore it.
Walk the whole thing yourself before anyone else can: Previewing and Testing Your Portal. When you are happy, go on to Publishing and Launching Your Participant Portal.