---
title: "Glossary"
slug: "glossary"
tags: ["reference-guides"]
status: "update"
updated: 2026-10-13T18:17:52Z
published: 2026-10-13T18:17:52Z
canonical: "docs.unqork.io/glossary"
---

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

# Glossary

Definitions of key terms used across Unqork documentation. Where a term has a specific meaning in Unqork that differs from common industry usage, that distinction is noted.

## A

**Agentic Smart Components**: A type of Smart Component that delivers AI-powered experiences to end-users at runtime. Agentic Smart Components connect to an organization-provided LLM and are not deterministic. See [Smart Components](/unqorkai/docs/smart-components-overview).

**API (Application Programming Interface)**: A defined set of rules that lets one software system communicate with another. In Unqork, Creators interact with APIs through the Plug-In component to send and receive data from external systems. Unqork also exposes its own API for reading and writing submissions, managing accounts, and triggering module execution programmatically.

**Anonymous Access**: Access to an Express application without requiring the end-user to log in. Anonymous access is enabled by default and can be disabled in [Environment Administration](/unqorkai/docs/environment-administration).

**Application**: A collection of modules organized and published for end-users. In Unqork, applications are also referred to as Express applications. Creators build and manage applications in workspaces. When promoted to a production environment, an application becomes the front-end that end-users interact with directly. Unqork supports two application types: **Module Type applications**, which deliver screens and forms built in the Module Builder, and **Workflow Type applications**, which use the Workflow Builder to drive multi-step processes across user interactions and automated tasks.

**Application (Module Type)**: An application that delivers screens and forms built in the Module Builder. End-users navigate through module pages to complete tasks, submit data, or view information. See [Module Builder](/unqorkai/docs/module-builder-overview).

**Application (Pre-Production)**: A version of an application in the optional Pre-Production environment level, which uses the Production codebase and enforces the same restrictions as Production. It is the only non-Production environment that runs the production build configuration (compressed, source maps removed) and blocks draft operations. Pre-Production holds test data only, not live client data. See [Environment Levels](/unqorkai/docs/environment-levels).

**Application (Production)**: The live version of a Creator-built application accessible to end-users, where live client data is stored. A Production application has been promoted through the environment pipeline. Draft-based development is blocked in Production; all changes must be promoted from a lower environment. See [Working in Production](/unqorkai/docs/working-in-production) and [Environment Levels](/unqorkai/docs/environment-levels).

**Application (QA)**: A version of an application in the Quality Assurance environment level, where Creators, QA engineers, and testers verify functionality and catch issues before the application advances toward Production. QA runs the development build configuration (source maps on), making it the recommended environment for debugging technical issues. QA hosts test data only. See [Environment Levels](/unqorkai/docs/environment-levels).

**Application (Staging)**: A version of an application in the Staging environment level, where Creators build and configure it before promoting to QA. Staging is the starting point of the promotion pipeline and runs the development build configuration (source maps on). Staging hosts test data only. See [Environment Levels](/unqorkai/docs/environment-levels).

**Application (UAT)**: A version of an application in the User Acceptance Testing environment level, where business stakeholders and end-users review and accept the application before Production. UAT runs the production build configuration (compressed, source maps removed), so stakeholders test the application in the same technical state end-users will experience. UAT hosts test data only. See [Environment Levels](/unqorkai/docs/environment-levels).

**Application (Workflow Type)**: An application that uses the Workflow Builder to drive multi-step processes across user interactions and automated tasks. End-users move through workflow steps as the workflow routes between nodes, completing forms, waiting for approvals, or receiving notifications. See [Workflow Builder](/unqorkai/docs/workflow-builder-1).

**Attribute Mapping**: A configuration in an SSO setup that maps a claim from the identity provider to a Unqork account attribute. For example, the `email` claim can be mapped to the Unqork `userId` field. See [Single Sign-On (SSO) Management](/unqorkai/docs/single-sign-on-sso-management).

## B

**Branch**: A named development line in the Application Versioning system where Creators make changes to an application before publishing to a version. Branches are the primary working context for application development. Creators can work in separate branches simultaneously without affecting each other. Branch operations are not available in Production or Pre-Production environments. See [Application Versioning](/unqorkai/docs/application-versioning-overview).

**Boundary Event**: A node in the Workflow Builder that attaches to another node and fires when a specific condition occurs, like an error, a timeout, or a met condition. Unlike regular nodes, boundary events are placed directly on their parent node. See [Swimlane Rules](/unqorkai/docs/swimlane-rules).

**Build Agent**: The UnqorkAI AI assistant integrated into the Module Builder. Creators describe what they want to build in plain language, and the Build Agent creates a plan, builds the components, connects the logic, and runs tests automatically. The Build Agent can also be referred to as the agent. See [UnqorkAI](/unqorkai/docs/unqorkai).

**Business Process Model and Notation (BPMN)**: A widely used notation for modeling business processes visually. Unqork's Workflow Builder is inspired by BPMN concepts, though it uses Unqork-specific terminology in some areas.

**BYO (Bring Your Own Component)**: A feature that lets Creators build custom Unqork components using third-party JavaScript libraries and custom code.

## C

**Canvas**: The central editing surface in the platform where a Creator works on an application (a module, workflow, or other artifact).

**Certificate Authority (CA)**: An organization that issues and digitally signs certificates, vouching for the identity of the entity named in the certificate. Common examples include DigiCert and Let's Encrypt. See [Certificate Concepts](/unqorkai/docs/certificate-concepts).

**Checkpoint**: A saved state of a module captured during a Build Agent session. Creators can restore a module to any checkpoint if a subsequent change produces unwanted results. See [UnqorkAI](/unqorkai/docs/unqorkai).

**Claim**: A piece of identity information provided by an identity provider during SSO authentication, for example, an email address or group membership. Claims are mapped to Unqork account attributes using attribute mapping. See [SSO Concepts](/unqorkai/docs/single-sign-on-sso-concepts).

**Component**: A building block placed on the Module Builder canvas. Components can collect input, display content, execute logic, or connect to external systems. Each component has a Property ID that uniquely identifies it in a module.

**Config View**: The Module Builder view that displays all components on the canvas alongside their settings panels. Creators use Config View to configure component properties, inputs, outputs, and actions. The View Toggler switches between Config View, UI View, and Logic View.

**Content Security Policy (CSP)**: A browser-enforced security standard that controls which external resources an Express application is allowed to load. Configured in [Environment Administration](/unqorkai/docs/environment-administration). See [Environment Security Concepts](/unqorkai/docs/environment-security-concepts).

**Cross-Origin Resource Sharing (CORS)**: A browser mechanism that controls which external origins are allowed to make API requests to the Unqork environment. Configured in [Environment Administration](/unqorkai/docs/environment-administration). See [Environment Security Concepts](/unqorkai/docs/environment-security-concepts).

**Creator**: The person who builds applications in Unqork. The term Creator is specific to Unqork. In the broader industry, this role is typically called a developer, configurator, or low-code builder.

**currentUser**: A built-in object available in Unqork modules during server-side execution that contains information about the logged-in end-user, including their ID, name, email, role, and group memberships. See [currentUser Object](/unqorkai/docs/currentuser-object).

## D

**Data Workflow**: A Module Builder component that executes a configurable pipeline of data operations in sequence, like API calls, transformations, filtering, and sorting. Creators build the pipeline visually using operators on the Data Workflow canvas. In Unqork, Data Workflow is a component, not the same as a workflow built in Workflow Builder.

**Data Workflow Operator**: An individual step in a Data Workflow component's pipeline. Each operator performs a specific function, like calling an API, filtering a dataset, or transforming a value. Operators are connected on the Data Workflow canvas to define the order of execution.

**Discoverable**: See **Public**.

**Domain (SSO)**: The type of account an SSO configuration applies to. Unqork supports two SSO domains: **Express** (Express application end-users) and **Designer** (Creators). See [SSO Concepts](/unqorkai/docs/single-sign-on-sso-concepts).

**Dot Notation**: A syntax for navigating a nested data structure by chaining property names with periods, for example, `currentUser.email` or `data.address.city`. In Unqork, is the standard way to reference specific values in submission data and system objects. In component output and input settings, dot notation wires data between components and inserts dynamic values in template expressions. It also accesses properties like name, email, and role from the currentUser object. See [Template Expressions](/unqorkai/docs/template-expressions) and [currentUser Object](/unqorkai/docs/currentuser-object).

**Draft (Smart Component)**: The unpublished working state of a Smart Component in the Smart Component Editor. Changes made in the editor are saved as a draft and are not visible to Creators using the component in their modules until the draft is published. See [Smart Component Editor](/unqorkai/docs/smart-component-editor).

## E

**End-User**: A person who interacts with a published Express application. End-users are the intended audience of a Creator's application. In Unqork documentation, "end-user" always refers to the end-user of an Express application, not the Creator.

**Express Group**: A named collection of end-users in an environment. Groups are used to assign shared access and roles to multiple end-users at once. Creators manage groups in [Express Group Administration](/unqorkai/docs/express-group-administration). Groups are promotable between environment levels.

**Express Role**: A set of permissions that controls what end-users can access and do in an Express application. Roles are assigned to end-users and determine which modules, pages, and data they can see. Creators manage roles in [Express Role Administration](/unqorkai/docs/express-role-administration). Roles are promotable between environment levels.

**Entrypoint**: The primary module of an application. The Entrypoint module is the first module an end-user accesses when they navigate to the application's URL. Each application has one designated Entrypoint.

**Environment**: A deployment of the UnqorkAI platform with its own configuration, data, accounts, and modules. Organizations typically have separate environments for development, staging, and production.

**Explorer**: The left-side navigation panel in the UnqorkAI platform that lists workspaces, applications, modules, and workspace resources. Creators use the Explorer to navigate between resources and access workspace, application, and module actions. In the Module Builder, the Explorer is accessible as the Explorer tab in the left panel. See [Explorer](/unqorkai/docs/explorer-overview).

**Express**: 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 platform.

**Express View**: A Creator-facing preview and troubleshooting mode in the UnqorkAI platform. Express View opens a module or application in a full browser tab at the same URL an end-user would visit, with a preview bar at the top that provides debugging controls and user-selection tools. Creators use it to verify behavior, test role-based access, and inspect network activity. End-users do not see the preview bar. See [Viewing and Previewing Applications](/unqorkai/docs/viewing-previewing-applications).

## G

**Genesis User**: The initial administrator account created when an environment is first provisioned. The genesis user exists before any other Creators are added and is used to complete initial environment setup.

**Global Variable**: A key-value pair defined at the environment level and accessible across all modules in that environment. Managed in [Global Variables Administration](/unqorkai/docs/global-variables-administration).

## I

**Integrated Development Environment (IDE)**: The browser-based workspace where Creators build, edit, review, and manage Unqork applications. Also referred to as the UnqorkAI platform.

**Identity Provider (IdP)**: An external system that authenticates Creators and end-users and provides identity information. Common examples include Okta, Microsoft Entra ID (formerly Azure AD), and Ping Identity. Used in SSO configurations. See [SSO Concepts](/unqorkai/docs/single-sign-on-sso-concepts).

## J

**JavaScript**: A programming language used in Unqork's BYO (Bring Your Own Component) feature, which lets Creators build custom components using JavaScript libraries and custom code. JavaScript is not directly editable in standard Unqork modules; it is used in BYO components and in external services that Unqork calls through the Plug-In component. See [BYO](/unqorkai/docs/byo-component).

**JSON (JavaScript Object Notation)**: A lightweight, text-based format for storing and transmitting structured data. In Unqork, JSON is the underlying format for submission data, API request and response bodies, module definitions, and configuration payloads. Creators encounter JSON when working with the API, configuring Plug-In components, or using dot notation to reference nested data.

**JSON Web Token (JWT)**: A compact, signed token used to verify a user's identity and maintain their session. In Unqork, JWTs are used to authenticate end-user sessions in the published application. Session behavior is configured in [Environment Administration](/unqorkai/docs/environment-administration). See [Environment Security Concepts](/unqorkai/docs/environment-security-concepts).

## L

**Locale Module**: A system module that stores all translation data for an application. Because translation data is stored in the Locale module instead of in individual modules, the Locale module must be promoted separately when moving an application across environment levels. See [Translations](/unqorkai/docs/translations-1).

**Logic Smart Component**: A Smart Component type that encapsulates reusable server-side logic (API calls, data transformations, or business rules) without a visible UI. Logic Smart Components can be shared across modules and applications. Previously called a Logic Block. See [Smart Components](/unqorkai/docs/smart-components-overview).

**Logic View (Module Builder)**: The Module Builder view that displays how data flows between components, showing the input and output connections that wire values across a module. The View Toggler switches between Logic View, UI View, and Config View. See [Logic View](/unqorkai/docs/logic-view).

**Logic View (Smart Component)**: The view inside the Smart Component Editor that displays the internal logic structure of a Smart Component, including how its operations, inputs, and outputs are connected. Separate from the Module Builder Logic View, which shows connections between components in a module. See [Smart Component Editor](/unqorkai/docs/smart-component-editor).

## M

**Merge**: An Application Versioning operation that combines the changes from one branch with another. The Complete Merge dialog offers two strategies: **Replace** integrates the source branch's changes into the target branch directly, and **Combine** creates a new branch from the combined result of both. Merge is not available in Production or Pre-Production environments. See [Application Versioning](/unqorkai/docs/application-versioning-overview).

**Module**: In Unqork, a module is a single application screen or form built in Module Builder. In most development contexts, "module" refers to a reusable code unit. The Unqork meaning is specific to its platform.

**Module Builder**: The Unqork tool used to build individual modules by placing and configuring components on a canvas.

**Mutual TLS (mTLS)**: An extension of TLS in which both the client and the server present certificates to verify each other's identity. Used in Unqork service connections to authenticate outbound requests. See [Certificate Concepts](/unqorkai/docs/certificate-concepts).

## O

**OpenID Connect (OIDC)**: A modern authentication protocol built on OAuth 2.0 that uses JSON-based tokens to authenticate users. One of two SSO protocols supported by Unqork. See [SSO Concepts](/unqorkai/docs/single-sign-on-sso-concepts).

**Link**: A connection between two nodes in the Workflow Builder that defines the the workflow follows. Output links can carry conditions that determine whether the link is followed and can be configured to display a flash message or run asynchronously. See [Output Links](/unqorkai/docs/output-links).

**Output Type**: A setting in component outputs that specifies what operation to perform when writing a value to a field, for example, assigning a value, appending to an array, or clearing a field. See [Output Types](/unqorkai/docs/output-types-reference).

## P

**PFX (PKCS#12)**: A binary file format that bundles a certificate and its private key into a single file. Unqork uses PFX certificates for SAML SSO signing and Mutual TLS service connections. See [Certificate Concepts](/unqorkai/docs/certificate-concepts).

**Plan**: The specification the Build Agent produces before configuring an application. A plan captures current versus future behavior, component-level configuration intent, and acceptance tests. Plans are scoped to a single task.

**Private**: A Smart Component visibility setting that restricts the component to the module where it was created. A Private Smart Component does not appear in the component tray and cannot be placed in other modules. Contrast with **Public**. See [Smart Components](/unqorkai/docs/smart-components-overview).

**Promote / Promotion**: The process of moving a resource from one environment level to the next in the promotion pipeline. Resources begin in Staging and progress through QA, UAT, and optionally Pre-Production before reaching Production. Express roles, Express groups, styles, and translations must each be promoted separately. See [Promoting Resources](/unqorkai/docs/promoting-resources) and [Environment Levels](/unqorkai/docs/environment-levels).

**Property ID**: The unique identifier assigned to a component in a module. Property IDs are used to reference component values across the module and in API calls. See [Property ID Naming Conventions](/unqorkai/docs/property-id-naming-conventions).

**Public**: A Smart Component visibility setting that makes the component available in the component tray for all Creators in the environment. A Public Smart Component can be placed in any module. Editing a Public Smart Component propagates the change to every module that uses it. Contrast with **Private**. See [Smart Components](/unqorkai/docs/smart-components-overview).

**Publish (Application Versioning)**: The action that converts the working state of a branch into a named, versioned snapshot. Publishing a branch creates a version that can be set as the default or used as a restore point. Published versions are stored in the application's version history. See [Application Versioning](/unqorkai/docs/application-versioning-overview).

**Publish (Smart Component)**: The action that makes a Smart Component's current draft the active version. Publishing applies the changes immediately across every module that uses the component. Unpublished changes exist only as a draft visible to the Creator who holds it. See [Smart Component Editor](/unqorkai/docs/smart-component-editor).

## Q

**Query Parameter**: A key-value pair appended to a URL after the `?` character, used to pass data to a web page or API endpoint. Multiple query parameters are separated by `&`. For example, in `https://example.com?userId=123&limit=50`, `userId=123` and `limit=50` are query parameters.

**Query Smart Component**: A Smart Component that wraps a Query Builder query and exposes it as a reusable component. Creators place Query Smart Components in modules to run the underlying query without reconfiguring it each time. See [Smart Components](/unqorkai/docs/smart-components-overview).

## R

**Record**: Data stored through a [Data Model](/unqorkai/docs/data-models-overview). Records are validated against the Data Model's schema, which enforces field types, required fields, and validation rules at the data layer. "Record" is also used informally as a synonym for "submission"; the two share the same underlying storage, but records created through a Data Model are always schema-validated. See [Data Models](/unqorkai/docs/data-models-overview) and [Record Collections](/unqorkai/docs/record-collections).

**Refer String**: An encrypted token generated by the Unqork API that authenticates an end-user into an Express application through a URL. Refer strings are commonly used in notification emails to give end-users a direct link to a module without requiring them to log in manually. See [Refer Strings](/unqorkai/docs/refer-strings-1).

**Regex (Regular Expression)**: A sequence of characters that defines a pattern for matching text. Used in Unqork components to validate end-user input, for example, requiring a field to contain only digits or match a specific format. See [Regular Expression Patterns](/unqorkai/docs/regular-expression-patterns).

**Role-Based Access Control (RBAC)**: A security model that restricts access to resources and functionality based on assigned roles. In Unqork, RBAC governs what Creators can access in the platform and what end-users can access in Express applications. See [Creator Role Administration](/unqorkai/docs/creator-role-administration) and [Express Role Administration](/unqorkai/docs/express-role-administration).

**Rollback**: A Build Agent action that restores a module to a previously saved Checkpoint, undoing all changes made since that checkpoint was created. See [UnqorkAI](/unqorkai/docs/unqorkai).

## S

**Security Assertion Markup Language (SAML)**: An XML-based authentication protocol that exchanges signed assertions between an identity provider and a service provider. One of two SSO protocols supported by Unqork. See [SSO Concepts](/unqorkai/docs/single-sign-on-sso-concepts).

**Server-Side Execution**: Processing that runs on the Unqork server instead of in the browser. Certain components and services can be restricted to server-side execution only for security purposes.

**Service**: A reusable configuration in Unqork that defines how a module connects to an external system, including authentication method, host, and headers. Services are managed in [Services Administration](/unqorkai/docs/services-administration).

**Service Provider (SP)**: The application that relies on an identity provider for authentication. In Unqork SSO configurations, Unqork is the service provider. See [SSO Concepts](/unqorkai/docs/single-sign-on-sso-concepts).

**Single Sign-On (SSO)**: An authentication method that lets Creators log in once through an external identity provider and access Unqork without managing a separate password. Configured in [Single Sign-On (SSO) Management](/unqorkai/docs/single-sign-on-sso-management).

**Smart Component**: The Unqork component architecture that ensures governance, security, and architectural best practices in applications. Smart Components come in four types: **Logic Smart Components** (reusable server-side logic), **UI Smart Components** (reusable visual interfaces), **Query Smart Components** (reusable queries), and **Agentic Smart Components** (AI-powered components created by the Build Agent or provided by Unqork, like the AI Summarizer). Creators cannot create Agentic Smart Components manually. All Unqork components are Smart Components. See [Smart Components](/unqorkai/docs/smart-components-overview).

**Smart Component Editor**: The tool in the UnqorkAI platform where Creators build, configure, and publish Smart Components. The Smart Component Editor provides a canvas for placing Logic Smart Components and UI Smart Components, a logic view for connecting data flows, and publish controls for releasing the component to the Smart Components Hub. See [Smart Component Editor](/unqorkai/docs/smart-component-editor).

**Smart Components Hub**: The catalog of Smart Components available in an environment, accessible from the Module Builder. Creators browse, search, and add Smart Components to their modules from the Smart Components Hub. Previously called the Smart Components Hub. See [Smart Components Hub](/unqorkai/docs/smart-component-hub).

**Snippet**: A saved, reusable configuration of one or more components that can be inserted into any module. Snippets let Creators standardize common patterns across applications without rebuilding them from scratch. Snippets are also a listing type in the [Marketplace Templates Administration](/unqorkai/docs/marketplace-templates), where module-level components like modals and drop-down lists are distributed by Unqork and verified partners. See [Saving a Snippet](/unqorkai/docs/saving-a-snippet-1).

**Submission**: The data saved when an end-user completes and submits a module. Submissions are stored and can be queried through the API. See [Submission Data Structure](/unqorkai/docs/submission-data-structure).

**Swimlane**: A horizontal lane in the Workflow Builder canvas that defines the execution context for nodes. Unqork has two swimlanes: **Automated** (server-side) and **Authenticated** (end-user interaction). The term swimlane is specific to Unqork. In Business Process Model and Notation (BPMN), these are called pools or lanes. See [Swimlane Rules](/unqorkai/docs/swimlane-rules).

## T

**Task**: A single unit of work in a Build Agent Plan. Each task maps to one configuration change or feature addition. The Build Agent completes tasks in sequence and runs acceptance tests after each one to verify the result. See [UnqorkAI](/unqorkai/docs/unqorkai).

**Template Expression**: A way to insert dynamic values into Workflow Builder node settings using double curly brace syntax, for example, `{{ data.firstName }}` or `{{ currentUser.email }}`. Values are resolved at runtime from submission data, system variables, or global variables. See [Template Expressions](/unqorkai/docs/template-expressions).

**Test**: Auto-generated acceptance tests based on requirements, intended behavior, and edge cases that verify what was built matches a Creator's definition of done. Creators can also add their own acceptance tests for the Build Agent to validate.

**Theme**: A set of style overrides applied to a Smart Component to control its visual appearance. Themes are managed in the Theme Editor and can be applied to individual Smart Components or shared across multiple. See [Smart Components](/unqorkai/docs/theme-editor).

**Transform**: A reusable data transformation configuration applied to module data at runtime. Transforms are defined in the Module Builder and can manipulate, format, or restructure submission data before it is used or displayed. See [Transforms](/unqorkai/docs/transforms-1).

**Trigger**: The event or condition that causes a component to execute. Common triggers include module load, a field value change, or a button click. Trigger behavior is configured in a component's Actions settings.

## U

**UI Smart Component**: A Smart Component type that encapsulates a reusable visual interface (a form, display element, or interactive pattern) that can be placed in any module. UI Smart Components expose inputs and outputs for wiring data to and from the surrounding module. Previously called a UI Block. See [Smart Components](/unqorkai/docs/smart-components-overview).

**UI View**: An inline viewing mode in the Module Builder that renders the module on the canvas without opening a new browser tab. Creators use UI View for quick visual checks and Console-based debugging without leaving the builder. See [Viewing and Previewing Applications](/unqorkai/docs/viewing-previewing-applications).

**UnqorkAI**: The AI-powered capability suite in the UnqorkAI platform. UnqorkAI includes the Build Agent for natural-language application building, Smart Components for governed reusable logic and UI patterns, and agentic component patterns for deploying AI agents in end-applications. See [UnqorkAI](/unqorkai/docs/unqorkai).

## V

**Version (Application)**: A published, named snapshot of an application in the Application Versioning system. Creators publish a branch's draft to create a version, which can then be set as the default or deployed. Versions provide a stable history of the application that can be restored or compared. See [Application Versioning](/unqorkai/docs/application-versioning-overview).

**View Toggler**: The drop-down control in the Module Builder toolbar that switches the canvas between UI View, Logic View, and Config View.

## W

**Workflow Builder**: The Unqork tool used to design and automate multi-step processes using a visual node-based canvas.

**Workflow Node**: An individual step in a workflow built in Workflow Builder. Each node performs a specific function, like presenting a form to an end-user, executing server-side logic, routing to different paths, or ending the workflow. Nodes are connected on the Workflow Builder canvas to define the flow of execution.

**Workspace**: The top-level container in Unqork that groups applications and controls who can access them.

## X

**X.509**: The standard format for digital certificates, defining the structure of a certificate including its subject, issuer, validity period, and public key. Unqork uses X.509 certificates for SAML SSO and Mutual TLS. See [Certificate Concepts](/unqorkai/docs/certificate-concepts).

---

**Changelog**

| Date | Change |
| --- | --- |
| 2026-09-14 | Renamed Discoverable → Public (now a redirect); added Public entry; updated Private contrast to Public; added Publish (Smart Component) entry. |
| 2026-09-18 | Renamed "Agentic Components" to "Agentic Smart Components"; updated definition to remove outdated release reference. |
| 2026-09-13 | Updated Smart Component definition: four types (added Agentic Smart Components — Build Agent-created and Unqork-provided like the AI Summarizer). |
| 2026-08-29 | Added 16 new entries: Checkpoint, Config View, Discoverable, Draft (Smart Component), Explorer panel, Logic Smart Component, Logic View, Private, Query Smart Component, Rollback, Smart Component Editor, Smart Components Hub, Task, Theme, UI Smart Component, UnqorkAI; updated Smart Component definition to reference all three types; updated Express View definition. |

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.

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.

Large Language Models (LLM) are artificial intelligence (AI) programs that use deep learning algorithms to analyze and generate text and other content based on large amounts of data.

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.

In Unqork an application is a program used to perform specific tasks. An application can be one of two types: workflow or module.

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

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.

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.

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

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

Use your QA (quality assurance) environment to test applications to ensure reliability, security, and functionality before releasing them to the end-user.

The Staging environment is the first level of application building in Unqork. Use it to build, test, and style your applications.

Use the UAT (user acceptance testing) environment to realistically test and navigate your applications as end-users would use them.

Single Sign-On is an authentication scheme that enables users to use one set of login credentials across multiple services.

Identity provider (IdP) provide a service that creates, manages, and verifies users' digital identities, allowing them to securely authenticate and access different applications or services.

A functionality of a software. For example, Copy and Paste is a feature of a computer's operating system.

JavaScript is an object-oriented computer programming language. It is most-commonly used for interactive effects in the browser.

A Property ID is the unique field ID used by Unqork to track and link components in your module.

The UI (user interface) is a device's end-user interaction and communication point. It can include display screens, keyboards, and mouse. It is also how a user interacts with your application.

A CSP (cloud service provider) is a company that delivers cloud computing services like storage, databases, and infrastructure to organizations over the internet, allowing users to access computing power, data storage, and applications on demand without managing their own physical hardware, typically paying only for the resources they use.

Cross-Origin Resource Sharing (CORS) lets you control access to resources located outside a given domain.

An object is a type of data structure that represents a single, self-contained entity that acts as a container for the characteristics of that entity.

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

A definition

A data structure is the design used for organizing, using, and storing data.

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.

An object is a type of data structure that represents a single, self-contained entity that acts as a container for the characteristics of that entity.

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

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.

Genesis users access and use a specific software platform for managing data, developing applications, and setting permissions for other users in the system.

Identity provider (IdP) provide a service that creates, manages, and verifies users' digital identities, allowing them to securely authenticate and access different applications or services.

Okta is a cloud-based identity and access management (IAM) platform that helps organizations manage user identities, access rights, and credentials across multiple applications, websites, and databases.

JSON (JavaScript Object Notation) is an open standard file and data interchange format. Unqork uses JSON for submission (record) data.

A JSON Web Token is an Internet standard for creating data with optional signature and/or optional encryption whose payload holds JSON that asserts some number of claims. Tokens are signed either using a private secret or a public/private key.

Transport Layer Security (TLS) is a protocol that provides communication security across a network.

OIDC (OpenID Connect) is an identity authentication protocol that lets two applications share user information without exposing user credentials.

OAuth, or Open Authorization, is an authorization protocol that lets users grant third-party access to their information without sharing their passwords. OAuth is an industry standard that's used by many companies, including Google, Amazon, and Microsoft.

An array is a type of object that stores one or more data types. Data types supported in arrays include numbers, strings, and objects.

Security Assertion Markup Language (SAML) is a protocol that allows an identity provider (IdP) to send a user's credentials to a service provider (SP) to verify their identity and grant them access to a service.

A Property ID is the unique field ID used by Unqork to track and link components in your module.

An API endpoint is the location where an API receives requests for a specific resource on its server. It's the point of contact between an API client and an API server, and is usually a uniform resource locator (URL) that provides the location of the resource.

A query lets you retrieve, access, manipulate, and delete data in a database.

Schema is a declarative language that defines the structure, content, and constraints of the data.

A string is an object that represents a sequence of characters. Strings typically hold data represented in text form.

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.

Extensible Markup Language (XML) is markup language that lets you define and store data in a shareable way.

A query lets you retrieve, access, manipulate, and delete data in a database.

Rendering is the process of loading components and displaying the final result on the front-end screen.

X.509 certificates are digital documents that represent a user, computer, service, or device. A certificate authority (CA), subordinate CA, or registration authority issues X.509 certificates. Certificates contain the public key of the certificate subject. They don't contain the subject's private key, which must be stored securely.