The interface for everyone without an account
Customers, partners, field staff or your own team rarely need access to the whole database — they need a page that shows exactly their view. That is what you build here, from blocks, without programming.
Assembled from blocks
A page is a freely composed interface. You drop blocks onto the canvas: headings and text for context, embedded views and evaluations for the data, input fields for everything that should come back.
- Basic blocks — heading, paragraph, image, subpage and layout containers
- Special blocks — embedded views, evaluations, buttons and your own HTML
- Form field blocks — the same field types as in a form, in the middle of the content
- Two modes — build in the editor, try it out in the application — without publishing
A page becomes a portal
“Create portal link” gives the page a web address of its own. From then on you can share it or embed it in your website — without anyone having to create an account. As long as no portal link exists, the page stays internal.
- Its own address — share by link, email or QR code
- Embedded — as an iframe inside your own website layout
- Responsive — the same page on desktop, tablet and phone
- Internally governed — without a portal link the space roles apply: view, edit, manage
Guided processes instead of long pages
The stepper layout turns a page into a sequence: one step at a time instead of a form with forty fields. Conditional visibility brings in what fits the answer so far and leaves the rest out.
- Stepper layout — subpages as steps with progress and a way back
- Tab layout — for when order does not matter but responsibility does
- Conditional visibility — blocks appear depending on values — empty, true, equal, greater than
- Custom expressions — ApptiveScript states the condition when the presets fall short
Blocks, layouts and publishing
What a page is made of and what you can set when you share it.
Basic blocks
- Heading
- Splits the page into sections.
- Paragraph
- Explanatory text between the data.
- Image
- A logo, photo or sketch inside the layout.
- Subpage
- Another page reachable from here.
- Layout
- Columns and containers that carry the structure.
Special blocks
- Embedded view
- A table, a kanban board or a map right on the page.
- Evaluation
- Key figures from the data, without a detour through a table.
- Button
- Triggers an action or leads onwards.
- HTML
- Your own code for the cases that need it.
Form field blocks
- Input fields
- The same field types as in a form — in the middle of the page.
- Mixed with content
- Explanation, data and input side by side instead of separated.
- Written back to the grid
- What someone enters lands in the entry.
Layout & navigation
- Tab layout
- Subpages side by side as tabs.
- Stepper layout
- A guided process, step by step.
- Editor and application
- Building and trying out as two modes of the same page.
Conditional visibility
- is empty / is not empty
- For every field type.
- is true / is false
- For checkboxes and decisions.
- is equal / is not equal
- For select fields, text and numbers.
- is greater / less than
- For numbers and dates.
- Custom expression
- With ApptiveScript when the presets are not enough.
Publishing
- Create portal link
- The page gets a web address of its own.
- Embed
- As an iframe inside your existing website.
- Stay internal
- Without a portal link the page is only visible inside the space.
- Roles
- View, edit, manage — governed by the space.
Questions about pages and portals
What is the difference between a page and a form?
A form is built for quick capture and shows a list of fields. A page has a free layout: text, images, embedded views, evaluations and input fields can sit side by side. A page can replace a form when more context is needed.
Do visitors need an account?
No. Once you create a portal link, the page lives at its own address and can be opened without signing in. Without a portal link the page stays internal and follows the roles of the space.
Can I embed a portal in my existing website?
Yes. The page can be included as an iframe and then runs inside your own layout — at every screen size.
Is conditional visibility a form of access control?
No, and that matters: hidden blocks remain technically inspectable. Conditional visibility keeps a page clear, it does not protect anything. Where confidentiality is at stake, use separate pages and roles.
Can a page show and collect data at the same time?
Yes. An embedded view shows existing entries while form field blocks take new input — both on the same page.
Can pages be part of an automated process?
Yes. A flow can display a page or send a link to it and wait until someone has decided. That is the basis for approvals and long-running processes.
Build your first portal
Start for free, arrange your blocks, share the link. No credit card required.