Page Designer

Overview

The Page Designer is a layer that lets you build your own screens and forms visually on top of your Custom Entities and selected system data. You compose a page from blocks (list table, form, detail card, filter, button, text, tabs) — much like arranging ready-made parts side by side. This way you design the custom screens your team works on every day without writing code.

Pages and Forms are two separate but complementary structures. A page is a composition of arranged blocks. A form is a reusable object: you design it once, use it on several pages, and when you update the form every page that uses it updates automatically. Screens react to each other: when you select a row in a list, the detail card or form bound to that row instantly shows the related record.

Your design is edited on a draft and only becomes available to users once you publish it. Published pages appear dynamically in the menu and can be opened with a readable address (for example a link that includes a customer’s identifier). For safety, users only see published pages and only reach the data they are authorized for.

Who uses it

• Organization administrators / internal app builders: People who design, publish and add to the menu custom screens and forms for their team.
• Process owners: People who want a tidy screen for a specific workflow (for example a “customer detail page” or an “order entry form”).
• End users: Team members who open published pages from the menu and do their daily work. They only see data that is available and authorized for them.

For example, an operations team builds a single page showing orders in a list on the left and the selected order’s details in a card on the right; users open this page from the menu and work.

Step-by-step process

1. Create a new page. Start a new page from the Pages section and give it a name.
2. Place blocks. Add the blocks you need within a section, row and column layout: a list table, a detail card, a form, a filter, or text and buttons.
3. Bind a data source. For each data block, choose a source: one of your own Custom Entities or a read-only system table (projects, tasks, members). Decide which columns appear.
4. Connect the blocks. Bind the detail or form that should update when a row is selected to that list. This makes the screen react to selection.
5. Design forms. Design the forms you will reuse separately (pick fields, arrange order and labels) and place them on your pages.
6. Publish. When your design is ready, publish it. The published page becomes available to users, can appear in the menu, and can be shared with a readable address.

Process flow

flowchart TD
    A[Create a new page] --> B[Place blocks: list, form, detail, filter]
    B --> C[Bind a data source: Custom Entity or system table]
    C --> D[Connect blocks: update on selection]
    D --> E[Edit on the draft]
    E --> F{Ready to publish?}
    F -- No --> E
    F -- Yes --> G[Publish]
    G --> H[Appears in menu + readable address]
    H --> I[Users work with data they are authorized for]

Frequently asked questions

Do I need to know how to code to build a page? No. You build pages from ready blocks: list, form, detail, filter, text and button. You add each block, bind it to a data source and set its layout — all through a visual interface.

What is the difference between a page and a form? A page is the screen where blocks are brought together. A form is a reusable object: designed once, embedded in many pages. When you update the form, every page using it updates automatically — you do not redesign the same form over and over.

Does everything I design become available to users right away? No. Design happens on a draft and only becomes available once you publish. Users never see drafts; they only rely on the published version.

What data can pages show? They can show your own Custom Entities (with full access) and selected read-only system tables (projects, tasks, members). System tables are for viewing only, and sensitive personal information is not included in those sources.

Can I update another block when a row is selected in a list? Yes. You bind a list to a detail card or a form; when the user selects a row in the list, the bound block instantly shows that record’s information. This lets you build live screens that react to selection.

How do users reach a published page? Your published page can appear in the menu automatically and opens with a readable address. Each user only sees the data they are authorized for; access is always checked on the server.