---
title: "Module Settings"
slug: "module-settings"
updated: 2026-09-15T18:21:48Z
published: 2026-09-15T18:21:48Z
canonical: "docs.unqork.io/module-settings"
---

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

# Module Settings

Module Settings is where Creators configure module-level properties, execution behavior, workflow triggers, and access control.

To open Module Settings, select the ![EllipsisVertical](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/api_upload_20260915_174942_4b40a4587c6b4eb480631fe858209006.svg?sv=2026-02-06&spr=https&st=2026-11-01T01%3A44%3A31Z&se=2026-11-01T02%3A44%3A31Z&sr=c&sp=r&sig=2DIfe1A66kvmDy7DGVm0Ggk7qMo907jW5DiVKYn0Ngk%3D) ellipsis next to a module in the Explorer panel and select **Settings** from the drop-down.

The panel is organized into four sections.

## ![LayoutList](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/api_upload_20260915_174942_07d9f0d45fd84695a4b7fef3d7e03aa3.svg?sv=2026-02-06&spr=https&st=2026-11-01T01%3A44%3A31Z&se=2026-11-01T02%3A44%3A31Z&sr=c&sp=r&sig=2DIfe1A66kvmDy7DGVm0Ggk7qMo907jW5DiVKYn0Ngk%3D) Module Details

Module Details collects the module's identity and metadata. Required fields are noted below.

| Setting | Description |
| --- | --- |
| Module Name | The display name for the module as it displays in the UnqorkAI platform and the Explorer tab. Required. |
| Module Path | The URL-safe identifier used in API calls and routing. Click the copy button to copy it to the clipboard. Required. |
| Module ID | Read-only. A system-assigned unique identifier for the module. Click the copy button to copy it to the clipboard. |
| Module Description | A description of the module's purpose. Accepts up to 500 characters. |
| Runtime | The execution runtime for the module. Options: or **Vega (2.0)**. Centauri is the standard runtime. Select Vega for modules that use Vega-only components like iFrame, Image, Menu, Search Select, Simple Select, Vega Table, or Vega Chart. |
| Module Type | Sets the module's execution model. Options include: **API**, **Front-End**, or **Other (data storage, rerouting, and so on)**. Selecting **API** automatically enables **Server-side Execution Only** in the Module Settings section. Selecting **Front-End** automatically disables it. Required. |
| Tags | Categorization labels for organizing and searching modules. Enter a name to create a new tag, or select an existing one. |
| Data Models | Links the module to data model schemas for component bindings. Models already referenced by a component in this module cannot be removed. |
| Module Size | Read-only. Displays the current size of the module in KB or MB, in both the UnqorkAI platform and Express. |

## ![Settings](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/api_upload_20260915_174942_1bfb7b5f65f247089d074aaefcc75aea.svg?sv=2026-02-06&spr=https&st=2026-11-01T01%3A44%3A31Z&se=2026-11-01T02%3A44%3A31Z&sr=c&sp=r&sig=2DIfe1A66kvmDy7DGVm0Ggk7qMo907jW5DiVKYn0Ngk%3D) Module Settings

Module Settings controls execution behavior and Express display options for the module.

### General Settings

| Setting | Description |
| --- | --- |
| Load Submissions With Initial Module Version | When set to **ON**, this setting loads submissions using the module version that was active when the submission was first created, instead of the current version. |
| Enable Stagger Load | When set to **ON**, this setting loads module components incrementally instead of all at once, improving perceived performance for large modules. |
| Container Components' Propagate "Disabled" to Logic Components | When set to **ON**, this setting prevents logic components inside a disabled container from executing. Applies to Panel, Field Group, and Columns components. |
| Disable Default Main and Form Regions | When set to **ON**, this setting removes the default `main` and `form` HTML regions, letting you define custom container elements with custom role wrappers. |

### Server-side Execution

| Setting | Description |
| --- | --- |
| Server-side Execution Only | When set to **ON**, this setting restricts the module to server-side execution only. Creators with Designer permissions can still preview the module in Express. This setting is automatically enabled when **Module Type** is **API** and automatically disabled when **Module Type** is **Front-End**. |
| Act as Super-User when server-side executing | When set to **ON**, this setting executes all server-side calls for this module with super-user privileges, regardless of the calling user's role. Use only when integration tasks require administrative access. |
| Capture Only Certain Fields in SSE Logs | When set to **ON**, this setting restricts SSE logs to capture only the request and response body properties specified in the allow-lists below. When set to **OFF**, the full request and response body is logged. Visible when SSE logging is enabled for the environment. |
| ↳ Allowed Request Body Properties | The request body property paths to include in SSE logs. Enter each path in (for example, `data.user.name`). If no keys are added, the entire request body is logged. Use the **Add Allowed Request Body Property** button to add entries. Visible when **Capture Only Certain Fields in SSE Logs** is **ON**. |
| ↳ Allowed Response Body Properties | The response body property paths to include in SSE logs. Enter each path in dot notation (for example, `result.id`). If no keys are added, the entire response body is logged. Use the **Add Allowed Response Body Property** button to add entries. Visible when **Capture Only Certain Fields in SSE Logs** is **ON**. |

### Express Settings

| Setting | Description |
| --- | --- |
| Enable Tracker | When set to **ON**, this setting activates session tracking for the module and reveals the **Track User** and **Track Value** sub-settings. |
| ↳ Track User | When set to **ON**, this setting records the identity of the Creator or end-user interacting with the module. Visible when **Enable Tracker** is **ON**. |
| ↳ Track Value | When set to **ON**, this setting records field values during the session. Sensitive data is not obfuscated unless the component's RBAC is set to Obfuscate. Use the Protected Field component for fields that store sensitive information. Visible when **Enable Tracker** is **ON**. |
| Show Page Title | When set to **ON**, this setting displays the **Page Title** value in the browser tab, appending the workspace site name for context. Required for ADA compliance. |
| ↳ Page Title | The text that displays in the browser tab when this module is open in Express. Visible when **Show Page Title** is **ON**. |

## ![GitBranch](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/api_upload_20260915_174942_942c6794aafa4be6b130a91816599c5c.svg?sv=2026-02-06&spr=https&st=2026-11-01T01%3A44%3A31Z&se=2026-11-01T02%3A44%3A31Z&sr=c&sp=r&sig=2DIfe1A66kvmDy7DGVm0Ggk7qMo907jW5DiVKYn0Ngk%3D) Workflow Settings

Workflow Settings configures validation behavior and navigation triggers for modules used inside a Workflow application.

### Validation

| Setting | Description |
| --- | --- |
| Validate On Opening Submission | When set to **ON**, this setting runs field validation when a submission is opened, not only when navigating forward. |

### Workflow Navigation Triggers

Workflow Navigation Triggers apply only to default Workflow navigation and do not apply to Button components placed in the module. Post Trigger and Post Validate Trigger execute only when navigating forward.

| Setting | Description |
| --- | --- |
| Post Trigger | Selects the component to after a Workflow navigation step completes. Options include all components in the current module. |
| Post Validate Trigger | Selects the component to trigger after validation passes when navigating forward in a Workflow. Options include all components in the current module. |
| Post Save Trigger | Selects the component to trigger after the submission is saved during Workflow navigation. Options include all components in the current module. |

## User Permissions

User Permissions controls who can access this module in Express, using role-based access control (RBAC).

### Role-Based Access Control

| Setting | Description |
| --- | --- |
| Customize RBAC for This Module | When set to **ON**, this setting activates module-level RBAC and reveals the **Allow Access to Anonymous Users** setting and the permissions table below. When set to **OFF**, only roles with no-access environment permissions are restricted; all other roles have write access by default. |
| ↳ Allow Access to Anonymous Users | When set to **ON**, this setting lets unauthenticated users view this module. **Customize RBAC for This Module** must be **ON** for this setting to take effect. Visible when **Customize RBAC for This Module** is **ON**. |

### Module Role-Based Access Control

When **Customize RBAC for This Module** is **ON** and roles exist in the workspace, a permissions table displays below the toggles. Each row represents an Express role. Use the **Permission** drop-down in each row to set the module-level access for that role.

| Column | Description |
| --- | --- |
| Role (Express) | The name of the Express role as configured in the workspace. |
| Permission | The permission applied at the module level. Options include: **Inherit** (uses the role's default permission), **No Access**, **Read-Only**, or **Write**. |
| Effective Permission | The resolved permission for the role, taking module-level and role-default values into account. |
| Inherited From | Indicates whether the effective permission comes from a module-level override (**Module**) or the role's default settings (**Role Defaults**). |

---

**Changelog**

| Date | Change |
| --- | --- |
| 2026-07-07 | Updated access — Module Settings is now opened via the Explorer ellipsis menu (UQE-16028). |
| 2026-06-16 | Updated H1 to Module Settings; added Vega Table and Vega Chart to Runtime field; language sweep. |
| 2026-06-09 | Updated Runtime field to document both Centauri (1.0) and Vega (2.0) options. |
| 2026-06-02 | Removed Type column from all tables; integrated Read-only notes into descriptions; Front-End capitalization fix; "etc." → "and so on". |
| 2026-05-28 | Added Capture Only Certain Fields in SSE Logs and its sub-settings. |
| 2026-05-27 | Initial publication. |

Also known as Unqork Users, or Designer Users; is anyone who is inside the Unqork platform.

A URL (uniform resource locator) is a unique identifier used to locate a resource on the internet. Also known as a web address.

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.

A definition

A place on your operating system that stores recently copied content. The clipboard only stores one item at a time.

A runtime engine is software that runs on a computer to allow applications to execute.

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.

Front-End (FE) Modules act as the user interface (UI) that end-users see and interact with. FE Modules use Plug-Ins to securly connect to API Modules for executing API calls.

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.

HTML (Hyper Text Markup Language) is the standard markup language for for achieving font, color, graphic, and hyperlink effects when creating web pages.

Elements are are what you use to build Unqork applications. Elements include modules, workflows, Data Collections, Data Schema, and Record Collections.

Includes the Short Answer component, Long Answer component, Select Boxes, Radio component, Dropdown, Number component and Single Checkbox.

Server-Side Execute (SSE) means data is executed outside of the end-users browser. This increases security by preventing data from being manpulated by bad actors.

A JavaScript property is a member of an object that associates a key with a value. A JavaScript object is a data structure that stores a collection of properties.

A key-value pair is a fundamental data structure where a unique "key" is associated with a specific "value," used for organizing and retrieving data efficiently, like in dictionaries or databases.

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.

RBAC (Role-Based Access Control) is a method to control system access for authorized users. The role in RBAC refers to the levels of access employees have to a network.

The Post Trigger value fires after a component has completed its action. For example, post triggering a component to display the data received from a Plug-In component's API call.

RBAC (Role-Based Access Control) is a method to control system access for authorized users. The role in RBAC refers to the levels of access employees have to a network.

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.

The Centauri (v 1.0.0) runtime is the first-generation foundation of the Unqork Designer Platform. Centauri provides Creators a codeless experience for developing applications.