URL Structure

Every page in your app has a slug — a short path segment that determines the page's URL. The page's full URL is the app's base URL followed by the slug:

Example — Page URL from slug

App base URL: https://mycompany.unifyapps.com/app/ Page slug: order-details Full page URL: https://mycompany.unifyapps.com/app/order-details

The slug is set when the page is created and can be changed in Page Settings at any time — but changing it breaks any external links or bookmarks pointing at the old address.

The Navigator Panel

The Navigator panel (left rail in the builder) lists all pages and modules as a tree. Pages can be organized into folders. Each page entry has an overflow menu with actions:

Creating a New Page

Click Create New Page from the Navigator panel or page list. The Page Setup dialog presents the following options:

Page Settings

After a page is created, open Page Settings from the Navigator menu to configure it further. Settings are organized into sections:

General Settings

Events

The Events section in Page Settings is where page triggers (On Page Load, On Page Focus, etc.) are configured. See Loading States & Triggers for full details.

Permissions

Layer role-based access on top of the Privacy setting. Private pages are already limited to authenticated users; Permissions add finer control over which authenticated users or roles can access the page. Pages with insufficient permissions are silently hidden from the navigation in the published app.

Custom Code

Add page-level JavaScript or CSS that executes only when this page is open. Useful for third-party analytics snippets, page-specific CSS overrides, or legacy integrations.

Dynamic URLs

Dynamic URLs let a single page represent many different records by capturing a variable value from the URL path. This is how you build detail pages — one page design, many records.

Folder Types for Dynamic Segments

Dynamic URL segments are created by setting a folder's type in the Navigator:

Dynamic folders have a Mock value setting — a placeholder value used in the builder so the page can preview correctly without a real record ID.

Folder Redirects

A folder can be configured to Redirect to another page. When a URL matching the folder's path is visited without a child page match, the visitor is redirected to the target page. Path parameters captured from the URL can be passed to the redirect target.

Example — Dynamic URL structure for an order detail page

Folder: orders/ (static segment) Folder: :orderId/ (dynamic segment — captures order ID) Page: details (slug: "details") Resulting URL pattern: /orders/:orderId/details Example URL: /orders/ORD-2847/details In-page access: {{ page.params.orderId }} → "ORD-2847"

Navigating Between Pages

In-app navigation is controlled by the Go to Page action (and related navigation actions), configured in any interaction or event handler.

Go to Page Action

Example — Navigating to an order detail page from a table row

// On row click in an Orders table: Action: Go to Page Page: Order Details Dynamic Params: orderId: {{ currentRow.id }} // The resulting URL will be something like: // /orders/ORD-2847/details // In the Order Details page, access the param: // {{ page.params.orderId }} → "ORD-2847" // Then use it as a data source input to fetch the order.

Related Navigation Actions

Deep Linking

Because every page and every record has a deterministic URL, sharing deep links is built in. To share a link to a specific record:

1. Navigate to the detail page for the record

2. Copy the URL from the browser address bar

3. Share it — anyone with access to the app who opens the link lands on that exact record's detail view

This works because the dynamic URL segment captures the record ID in the path, and the On Page Load trigger uses that ID to fetch the correct record from the data source.

Example — Fetching a record from a deep-linked URL

// Shared URL: // /orders/ORD-2847/details // In the Order Details page, on Page Load: // Run data source: order_query // Input — orderId: {{ page.params.orderId }} // order_query fetches the specific order with id ORD-2847. // The page displays that order's data — same as if the user // had clicked through from the Orders list.

Privacy and Access

Every page has a Privacy setting that controls who can open it:

Permissions (role-based access) layer on top of Privacy. A Private page is first gated by authentication; Permissions then control which authenticated users can see the page.

Warning: No two pages can share the same URL slug. If you try to set a slug that is already used by another page, the platform will prevent the save and show a conflict error. Rename one of the pages to resolve the conflict.

Document Title

The document title is the text shown in the browser tab when this page is open. It can be:

Example — Dynamic document title on an order detail page

Document Title: Order {{ order_query.data.orderNumber }} — Acme App // While the page is loading: // Browser tab: "Order — Acme App" (orderNumber not yet resolved) // After data loads: // Browser tab: "Order ORD-2847 — Acme App"

The title updates automatically when the bound expression resolves — no extra actions required.

Query Parameters (Page Inputs)

Pages can accept input values via the URL query string. These are declared as Query Parameters in Page Settings and received by the page as named inputs.

Routing Summary

Note: Dynamic params (URL path segments like /orders/:orderId) are best for identifying the main subject of the page — the record being viewed. Query parameters (URL query string like ?tab=overview) are best for supplemental context like active tab, filter state, or display preferences. Both are readable in the page via expressions.