---
title: "What Is a Module?"
slug: "what-is-a-module"
updated: 2025-09-25T23:30:04Z
published: 2025-09-25T23:30:04Z
canonical: "docs.unqork.io/what-is-a-module"
---

> ## 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.

# What Is a Module?

**Module****s** are the building blocks of your [application](/v1/docs/introduction-to-unqork-applications). Unqork modules serve as a container for the rapid creation and management of business application data. In modules, Creators can add [components](/v1/docs/module-builder-component-library) to create the functionality needed for an application.

Here are some examples of what a module can do:

- Display forms, questionnaires, dashboards, and more for end-users.
- Connect to APIs to move data between software services and applications.
- Perform complex mathematical calculations based on end-user input.
- Update and manage stored data using SQL-like [operators](/v1/docs/data-workflow-operatorlibrary).
- Set up triggers to automate application and submission processes.

## Understanding Module Types

Unqork separates modules into three types: API, Front End, and Other-type modules. Each module type makes it easier to design them for a specific purpose.

Below is a description of each module type and the module settings enabled or disabled on creation:

| Module Type | Description | Default Settings |
| --- | --- | --- |
| **API** | An API-type module includes preconfigured components that meet Unqork API specifications for server-side/remote execution. An API tag is also added by default to ensure your module displays in the [API Docs Dashboard](/v1/docs/api-docs-dashboard-tool) tool. When creating a module in a Workflow [Task](/v1/docs/task-node) node positioned in the Automated swimlane, the API-type is selected by default. | When creating an API module, the **Server-Side Execution** setting is set to ![A toggle switch indicating an on/off state for a user interface element.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Group 1.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A48Z&se=2026-11-07T18%3A57%3A48Z&sr=c&sp=r&sig=EYtRgEXGO%2BhnV%2BZXTWpiFGDqYTuFXS%2FP0V%2BY6kFVlHg%3D) **(ON)** by default, and disabled. Disabling this setting promotes security best practices. |
| **Front-End** | A Front-End-type module is a module element built for user interfaces. When creating a module in a workflow Task node positioned in an Authenticated swimlane, the Front-End-type is selected by default. | When creating a Front-End module, the **Server-Side Execution** setting is set to ![A toggle switch in the 'on' position, indicating an active setting or feature.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Group 2(1).png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A48Z&se=2026-11-07T18%3A57%3A48Z&sr=c&sp=r&sig=EYtRgEXGO%2BhnV%2BZXTWpiFGDqYTuFXS%2FP0V%2BY6kFVlHg%3D) **(OFF)** by default, and disabled. Disabling this setting ensures this module type is always accessible in Express View. |
| **Other** | An Other-type module is for module elements that are not considered Front-End or API modules. This module type includes modules used for storing data, rerouting data, and so on. | When creating an Other-type module, the **Server-Side Execution** setting is set to ![A toggle switch in the 'on' position, indicating an active setting or feature.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Group 2(1).png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A48Z&se=2026-11-07T18%3A57%3A48Z&sr=c&sp=r&sig=EYtRgEXGO%2BhnV%2BZXTWpiFGDqYTuFXS%2FP0V%2BY6kFVlHg%3D) **(OFF)** by default. With Other-type modules, you can choose to set the Server-Side Execution setting to ![A toggle switch indicating an on/off state for a user interface element.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Group 1.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A48Z&se=2026-11-07T18%3A57%3A48Z&sr=c&sp=r&sig=EYtRgEXGO%2BhnV%2BZXTWpiFGDqYTuFXS%2FP0V%2BY6kFVlHg%3D) **(ON)****.** |

## Accessing a Module

U DesignerClassic Designer

### UDesigner

Modules exist inside Applications, which are inside Workspaces. You can access a module from your UDesigner homepage or the All Workspaces page by clicking **Workspaces** at the top of the Unqork Designer Platform.

### UDesigner Homepage

To access an existing module from your UDesigner homepage:

1. Locate the module in your **My Recents** or **Starred** elements
2. Click **View**.

Your module now opens in the Module Builder.

### All Workspaces

To access an existing module from the All Workspaces page:

1. At the top of your UDesigner homepage, click **Workspaces**.
2. From the Workspaces list, find and click the [workspace](/v1/docs/introduction-to-workspaces) name where the module exists, or click **View Workspace**.
3. From the Applications list, click the [application](/v1/docs/introduction-to-unqork-applications) name where the module exists, or click **View App**.
4. From the Application Elements list, click the module name, or click **View**. The module opens on a new page in the Module Builder.

You can now select components to drag and drop onto the Module Builder canvas and configure them to create applications.

### Classic Designer

Modules exist inside Applications, which are inside Workspaces. To access a module, Creators must be assigned to a workspace using WSRBAC (Workspaces Role-Based Access Control). You can access a module from the All Workspaces page by clicking **Workspaces** at the top of the Unqork Designer Platform.

### All Workspaces

To access an existing module from the All Workspaces page:

1. At the top of your UDesigner homepage, click **Workspaces**.
2. Click the [workspace](/v1/docs/introduction-to-workspaces) tile's name where the module exists, or click **View Workspace**.
3. Click the [application](/v1/docs/introduction-to-unqork-applications) tile's name where the module exists, or click **View App**.
4. Click the module tile's name, or click **View**. The module opens on a new page in the Module Builder.

[Video](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Module_Editor_AccessModule.webm?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A48Z&se=2026-11-07T18%3A57%3A48Z&sr=c&sp=r&sig=EYtRgEXGO%2BhnV%2BZXTWpiFGDqYTuFXS%2FP0V%2BY6kFVlHg%3D)

You can now select components to drag and drop onto the Module Builder canvas and configure them to create applications.

## Previewing Your Module

You can easily preview Front-End modules as you build them. The **Preview** button opens your module in Express View. Express View displays your application as your end-user sees it. Ensure you save your module first, as unsaved changes don't display in the preview.

> [!NOTE]
> Your module must have at least one component to preview it.

To preview your module in Express View:

1. Open your module in the Module Builder.
2. At the top right, click **Preview**.

> [!NOTE]
> You might be asked to log into your environment again to view your module in Express View.

You can now use Express View to preview how your end-users views your applications and test and troubleshoot it.

> To learn how to create and edit a module, view our [How to: Create a Module](/v1/docs/how-to-create-and-edit-a-module) article.

You’ll also notice that your application's Express View URL is different than the Module Builder URL. In Express View, the URL includes an appended **x**. For example, while **training.unqork.io** displays as the Module Builder URL, **trainingx.unqork.io** displays in Express View.

**Module Builder**:

[![A static image displaying the Module Editor URL.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/App_Intro_Designer_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A48Z&se=2026-11-07T18%3A57%3A48Z&sr=c&sp=r&sig=EYtRgEXGO%2BhnV%2BZXTWpiFGDqYTuFXS%2FP0V%2BY6kFVlHg%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/App%20Intro%20Designer.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A48Z&se=2026-11-07T18%3A57%3A48Z&sr=c&sp=r&sig=EYtRgEXGO%2BhnV%2BZXTWpiFGDqYTuFXS%2FP0V%2BY6kFVlHg%3D)

**Express View**:

[![A static image displaying the Express View URL.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/App_Intro_Express_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A48Z&se=2026-11-07T18%3A57%3A48Z&sr=c&sp=r&sig=EYtRgEXGO%2BhnV%2BZXTWpiFGDqYTuFXS%2FP0V%2BY6kFVlHg%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/App%20Intro%20Express.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A48Z&se=2026-11-07T18%3A57%3A48Z&sr=c&sp=r&sig=EYtRgEXGO%2BhnV%2BZXTWpiFGDqYTuFXS%2FP0V%2BY6kFVlHg%3D)

> To learn more about previewing your application, visit the [Application Introduction](/v1/docs/introduction-to-unqork-applications) article.

### Access Express Roles Using the Express Bar

When previewing a module in Express View, an Express bar displays at the top of the page. This bar lets Creators view the module as different [Express users](/v1/docs/express-user-administration) and adjust styles or runtimes. The Express bar is only visible to Designer users. It is not displayed for other Express users.

For example, clicking the **Preview As:** drop-down displays the following roles for an environment:

[![A static image displaying the Express View express bar. The Preview As dropdown is highlighted.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/expressViewRoleBar_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A48Z&se=2026-11-07T18%3A57%3A48Z&sr=c&sp=r&sig=EYtRgEXGO%2BhnV%2BZXTWpiFGDqYTuFXS%2FP0V%2BY6kFVlHg%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/expressViewRoleBar.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A48Z&se=2026-11-07T18%3A57%3A48Z&sr=c&sp=r&sig=EYtRgEXGO%2BhnV%2BZXTWpiFGDqYTuFXS%2FP0V%2BY6kFVlHg%3D)

### Previewing Your Module as an Application

Previewing a module in the application context. This includes the [Header module](/v1/docs/header-module) and [Footer module](/v1/docs/footer-module) in Express View.

To view your module as it would appear in your application:

1. Click the Preview button drop-down.
2. Select **Preview with App Context**.

[![A static image displaying the Module Builder's Preview with App Context button.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/previewApp_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A48Z&se=2026-11-07T18%3A57%3A48Z&sr=c&sp=r&sig=EYtRgEXGO%2BhnV%2BZXTWpiFGDqYTuFXS%2FP0V%2BY6kFVlHg%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/previewApp.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A48Z&se=2026-11-07T18%3A57%3A48Z&sr=c&sp=r&sig=EYtRgEXGO%2BhnV%2BZXTWpiFGDqYTuFXS%2FP0V%2BY6kFVlHg%3D)

You’ll also notice the Express View URL for previewing a module in the application context is different than previewing the module only. In the example below, previewing a module displays the module ID. Previewing a module in the application context displays `app/example-application#`, where `example-application` is the name of your application.

**Preview** **Module**:

[![A static image displaying the Module Editor URL.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/previewModule_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A48Z&se=2026-11-07T18%3A57%3A48Z&sr=c&sp=r&sig=EYtRgEXGO%2BhnV%2BZXTWpiFGDqYTuFXS%2FP0V%2BY6kFVlHg%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/previewModule.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A48Z&se=2026-11-07T18%3A57%3A48Z&sr=c&sp=r&sig=EYtRgEXGO%2BhnV%2BZXTWpiFGDqYTuFXS%2FP0V%2BY6kFVlHg%3D)

**Express View** **Preview** **Module** **as an Application**:

[![A static image displaying the Express View URL.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/previewModuleApp_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A48Z&se=2026-11-07T18%3A57%3A48Z&sr=c&sp=r&sig=EYtRgEXGO%2BhnV%2BZXTWpiFGDqYTuFXS%2FP0V%2BY6kFVlHg%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/previewModuleApp.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A48Z&se=2026-11-07T18%3A57%3A48Z&sr=c&sp=r&sig=EYtRgEXGO%2BhnV%2BZXTWpiFGDqYTuFXS%2FP0V%2BY6kFVlHg%3D)

> Discover how to connect Header and Footer modules to an application in our [Header Module](/v1/docs/header-module) and [Footer Module](/v1/docs/footer-module) articles.

## Resources

- [Create, Duplicate, Share, Move, or Delete a Module](/v1/docs/working-with-module-type-apps).
- [Copy and Paste Module Definitions](/v1/docs/how-to-copy-and-paste-module-definitions).
- [Best Practices for Configuring a Module](/v1/docs/best-practices-component-configuration).
- [How to Structure Modules](/v1/docs/introduction-to-structuring-modules).
- [Troubleshooting Common Issues in a Module](/v1/docs/common-performance-issues).
- [Discover More About Modules in the Community Hub](https://community.unqork.com/search?q=Modules).

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.

APIs (application programming interfaces) are a set of protocols and definitions developers use to build and integrate application software. APIs act as the connective tissue between products and services.

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.

SQL (Structured Query Language) is language used in programming and designed for managing data contained in a relational database system.

APIs (application programming interfaces) are a set of protocols and definitions developers use to build and integrate application software. APIs act as the connective tissue between products and services.

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.

WSRBAC (Workspaces Role-Based Access Control) is a method to control user access to a workspace. Users must be assigned to a workspace using WSRBAC before they can view or edit applications and modules inside the space.