--- title: "Working in Production" slug: "working-in-production" tags: ["applications"] status: "update" updated: 2026-10-15T14:22:59Z published: 2026-10-15T14:22:59Z canonical: "docs.unqork.io/working-in-production" --- > ## 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. # Working in Production Production is the only environment where live client data is stored and where end-users interact with the application. The UnqorkAI platform enforces specific restrictions in Production to protect live data and prevent unreviewed changes from reaching end-users. > [!CAUTION] > All development should take place in Staging and move to Production through the promotion pipeline; never directly in Production. The platform provides no warnings or confirmation dialogs when saving in Production, and every change goes live immediately. If a Creator saves a breaking change in Production, end-users encounter it with no automatic rollback. See [Recovering from an Accidental Production Edit](/unqorkai/docs/working-in-production#recovering-from-an-accidental-production-edit) if this happens. ## Identifying the Environment The platform does not display a dedicated banner or badge indicating the current environment. For standard Unqork-hosted environments, the URL is the primary signal: Production follows the pattern `{organization}-prod.unqork.io`, while non-production environments use patterns like `{organization}-staging.unqork.io`, `{organization}-qa.unqork.io`, or `{organization}-uat.unqork.io`. Environments with custom domains do not follow this pattern. ### Accessing the Platform on a Custom Domain When a Production environment uses a custom domain, the root URL (for example, `identity.unqork.io`) loads the Express application and does not provide a Creator login. To access the Creator platform on a custom domain, append `-designer` to the subdomain: ``` identity.unqork.io        → Express application (end-users) identity-designer.unqork.io  → Creator platform (Creators and administrators) ``` Use the `-designer` URL to access Environment Administration, Style Administration, and all other Creator surfaces in a custom-domain Production environment. Creators unsure which environment they are working in should confirm with their environment administrator before making changes. ## What the Platform Blocks in Production These restrictions are enforced server-side. Blocked actions do not appear in the UI or are rejected if attempted directly. ### Branch and Version Operations All draft-based development is blocked in Production. Draft-based development is the branching and versioning workflow available in non-production environments. See [Application Versioning](/unqorkai/docs/application-versioning-overview). | Blocked Action | Details | | --- | --- | | Creating a branch | The platform's draft system is not available in Production. | | Deleting a branch | All draft write operations are blocked server-side. | | Publishing a branch to a version | Blocked server-side. | | Combining branches | Blocked server-side. | | Complete Merge | Blocked: requires draft operations. | | Complete Combine | Blocked: requires draft operations. | | Moving a module to a new branch | Branch creation during the move is blocked. | ### Application Settings and Dependencies | Blocked Action | Details | | --- | --- | | Enable Versioning toggle | Disabled: requires application update permission, which Production removes. | | [Application Dependencies](/unqorkai/docs/application-dependencies) | Read-only: no edits possible in Production. | | [Smart Component Draft](/unqorkai/docs/smart-component-editor) | Blocked: requires a non-production environment. | ## What Is Available in Production The restrictions above are the complete list of what is blocked. Everything not listed is available in Production. **Promoting resources** is not blocked. Creators with the appropriate permissions can promote applications, styles, groups, roles, and translations from lower environments to Production. See [Application Promotions](/unqorkai/docs/application-promotions) and [Promoting Resources](/unqorkai/docs/promoting-resources). **All Administration pages** are available to Creators whose [Creator role](/unqorkai/docs/creator-role-administration) grants administration access. Production does not change or remove Creator role permissions. Available pages include: - [Environment Administration](/unqorkai/docs/environment-administration) - [Style Administration](/unqorkai/docs/style-administration-1) - [Creator (User) Administration](/unqorkai/docs/creator-user-administration) - [Express User Administration](/unqorkai/docs/express-user-administration) - [Express Role Administration](/unqorkai/docs/express-role-administration) - [Global Variables Administration](/unqorkai/docs/global-variables-administration) - [Services Administration](/unqorkai/docs/services-administration) - [Single Sign-On (SSO) Management](/unqorkai/docs/single-sign-on-sso-management) - All other administration surfaces **Viewing and previewing modules** is not blocked. The Module Builder is accessible in Production in read-only mode; the **View in Express** button is available for previewing modules. **UDLC Toolkit tools** (monitoring, logs, metrics, and other observability tools) are available to administrators after the toolkit is promoted to Production. See [UDLC Toolkit Overview](/unqorkai/docs/udlc-toolkit-overview). ## Common Production Tasks ### Changing the Default Style The environment's default style cannot be changed from Environment Administration; that page displays the current style as read-only text. The correct uses Style Administration: 1. In a non-production environment, create or update the style in **Style Administration**. 2. Promote the style to Production: in **Style Administration**, select the style, select **Promote**, and choose Production as the target environment. 3. In the Production environment, open **Style Administration**, find the promoted style, and select **Set as default**. The **Set as default** action in Style Administration is not blocked in Production. Only application draft operations are blocked. ### Updating Environment Configuration Environment-level configuration covers authentication settings, session management, security policies, and integrations. Each environment manages these settings independently. To update configuration in Production, open **Environment Administration** directly in the Production environment. Configuration changes in Environment Administration are not blocked by the production restrictions that apply to application drafts. ### Recovering from an Accidental Production Edit If a Creator saves a change directly in Production: 1. Identify the last known-good version in a lower environment (Staging or UAT). 2. Promote the known-good version from the lower environment to Production. Promoting overwrites the current Production version with the correct one. 3. Verify the restored version in Production. Do not attempt to fix the issue by making additional edits in Production. Restore from a lower environment instead. ## Pre-Production Has the Same Restrictions Pre-Production is an optional environment level that uses the Production codebase. All the same restrictions apply: draft-based development, Smart Component Draft, and every blocked action listed above are unavailable in Pre-Production. The only differences are that Pre-Production holds test data instead of live client data, and has a distinct URL. --- **Changelog** | Date | Change | | --- | --- | | 2026-10-15 | Qualified UDLC Toolkit availability: tools are available after the toolkit is promoted to Production. Editorial pass: capitalized Module Builder, corrected administration link names, replaced em dashes in table cells, changed "Your" in a heading, and converted the Administration page links to a list. | | 2026-08-31 | Added custom domain access pattern (`-designer` suffix). | | 2026-08-29 | Initial publication. | 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. 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 Staging environment is the first level of application building in Unqork. Use it to build, test, and style your applications. 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. 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. Also known as Unqork Users, or Designer Users; is anyone who is inside the Unqork platform. 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. The UDLC (Unqork Development Lifecycle) Toolkit is a set of tools designed to manage Unqork applications. Use the UAT (user acceptance testing) environment to realistically test and navigate your applications as end-users would use them.