--- title: "Express View Page" slug: "express-view-page" tags: ["previewing-applications"] updated: 2026-08-31T15:55:53Z published: 2026-08-31T15:55:53Z canonical: "docs.unqork.io/express-view-page" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.unqork.io/llms.txt > Use this file to discover all available pages before exploring further. # Express View Page The Express View page loads an application or module in the same front end that end-users use, with an additional preview bar visible only to Creators. This article explains the preview bar controls, describes how Express View handles data, and covers the difference between a Creator's Express View and the end-user's experience. ## Express View Preview Bar The preview bar displays at the top of the Express View page. It is visible to Creators only and does not appear for end-users. ![The Express View preview bar at the top of the page, showing the Preview as and Preview Style controls.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/base64-converted-image-1788191599030.png?sv=2026-02-06&spr=https&st=2026-11-08T18%3A09%3A04Z&se=2026-11-08T19%3A09%3A04Z&sr=c&sp=r&sig=J24hT2o0DWQnSVgkIObJ1lG5AE4M39NwPrV5TQJwpW4%3D) The preview bar provides the following controls: | Control | Description | | --- | --- | | **Preview Runtime as** | Switches the runtime engine used to render the application. Options are **Vega (2.0)** and . | | **Preview as** | Lets Creators select which Express role to preview the application as. Options include the available Express roles configured in the environment (for example, **Administrator**, **Authenticated**, **Anonymous**, **No Access**). Selecting a role loads the application with that role's permissions and data access applied. Creators can test restricted scenarios without logging in as a separate account. Learn more about creating end-user roles in [Express Role Administration](https://docs.unqork.io/unqorkai/docs/express-role-administration). | | **Preview Style** | Controls the style applied to the application in Express View. | | **Remove** | Hides the preview bar completely, showing the application exactly as end-users see it. | | **Hide** | Collapses the preview bar while keeping it accessible. | ## How Data Is Captured In Express View, data submitted or entered by a Creator is stored as real submission data in the environment. Express View does not use a sandbox or isolated data store. Any form submissions, record saves, or data writes made in Express View create or update actual records in the environment. Creators should use test accounts or clearly labeled test data when working in Express View to avoid creating records that affect production reports, workflows, or downstream processes. ## Creator Express View vs. End-User Experience The table below summarizes the differences between what Creators see in Express View and what end-users see in the production application. | Feature | Creators in Express View | End-Users in Production | | --- | --- | --- | | **Preview bar** | Visible at the top of the page. | Not visible. | | **User selector** | Can switch to any Express user account. | Does not see their account or others. | | **Console Tools** | Can run debugging commands in the browser console. | Cannot access console tools. | | **Data changes** | See saved changes immediately after saving in the platform. | Always see the last saved state of the application. | | **Unsaved changes** | Express View reflects the last saved version of the module. Save changes in the Module Builder before opening Express View to see updates. | Always see the last saved state. | | **Data written** | Writes real submission data to the environment. | Writes real submission data to the environment. | --- **Changelog** | Date | Change | | --- | --- | | 2026-08-28 | Accuracy pass: fixed "Unsaved changes" row; fixed description opener; corrected internal link ; removed slop note (EN-8063). | | 2026-05-11 | Initial publication. | Express View is how your end-user views your application. Express View also lets you preview your applications to test your configuration and view the styling. This is also the view your end-users will see when interacting with your application. After configuring a module, click Preview in the Module Builder to interact with the module in Express View. End-users, also known as Express Users, are the individuals accessing an application through Express View. In most cases, end-users are the customers using the product. Also known as Unqork Users, or Designer Users; is anyone who is inside the Unqork platform. End-users, also known as Express Users, are the individuals accessing an application through Express View. In most cases, end-users are the customers using the product. The Unqork front-end application framework that delivers Creator-built applications to end-users. Express is the layer end-users interact with—the published forms, screens, and navigation built in the Module Builder. Express is distinct from Express View, which is a Creator-facing preview tool in the IDE. Rendering is the process of loading components and displaying the final result on the front-end screen. The Vega (v 2.0.0) runtime is the next-generation engine of the UDesigner platform. Vega uses cutting-edge technologies to improve the Creator and end-user experience. Also known as Unqork Users, or Designer Users; is anyone who is inside the Unqork platform. The Production environment is the final stage of the development process. Use this environment to promote tested and functioning application so your end-user can interact with it.