Packaged installed applications
Packaged applications add a versioned product to a workspace. An application manifest defines the data model, access rules, server logic, user interface, settings, connections, messaging, agents, workflows, and other resources that the package provides. The public catalog supports review and installation. Installation turns one package version into workspace features that can be configured, updated, monitored, exported in supported cases, and removed. This page is part of the external integrations model.
Application package model
Application manifests
An application manifest is the product contract between a package, the public catalog, and a workspace. Each item has a stable universal identifier. This lets a later package version update the same workspace item instead of creating a new one.
The manifest groups the product definition into these areas:
| Manifest area | Product purpose |
|---|---|
| Application identity | Names the package and describes its version, support, billing, server needs, configuration, and runtime resources. |
| Workspace model | Adds objects, fields, indexes, related record paths, views, page layouts, navigation, settings, activity types, validation rules, and workflows. |
| Access and intelligence | Adds roles with record and field access rules, row-level rules, permission flags, skills, and agents. An agent can also receive an application role target. |
| Runtime behavior | Adds logic functions, connection providers, messaging providers, front components, commands, and MCP servers. An MCP server is a remote tool service exposed through a URL. |
| Package resources | Delivers public assets, translations, dependency files, built handlers, built front components, source files, and shared front-end dependencies. |
The same contract supports catalog packages and applications developed in a workspace. This keeps preview, install, update, export, and local sync aligned around one product description.
Package resources are part of the application trust boundary. Stored dependency files must match the checksums in the manifest before the application can use them. Source files can support development. Built runtime files provide the packaged behavior.
References: packages/…/manifestType.ts• L41-70 packages/…/applicationType.ts• L15-55 packages/…/roleManifestType.ts• L118-144 packages/…/build-application-file-list.util.ts• L19-123 packages/…/application-sync.service.ts• L264-347
Workspace configuration
Application configuration supplies values that differ between workspaces without changing the package. The model supports typed values and separates values that users may view or edit from server values that may hold secrets.
Required values are part of the install contract. An application is not ready for use until its required values are filled. Deprecated values can remain for migration without blocking setup. Values can use workspace or member scope. Secret values stay protected after they are saved.
Application key-value data is separate from manifest variables. It gives the package a small store for runtime state inside the application and workspace boundary. The store can also use member scope.
References: packages/…/compute-application-manifest-all-universal-flat-entity-maps.service.ts• L744-780 packages/…/applicationVariablesType.ts• L18-73 packages/…/applicationType.ts• L15-24
Workspace capabilities
An installed application adds executable behavior and workspace structure as one application-owned set. This ownership keeps permissions, links, updates, and removal consistent.
The main capability groups are:
- Business objects, fields, indexes, related record paths, validation rules, and views for application data.
- Page layouts, navigation, settings, and commands for the user experience.
- Roles, object and field rules, row rules, and permission flags for access control.
- Skills, agents, activity types, and workflows for reusable behavior.
- Connection providers, messaging providers, and MCP servers for external services.
- Front components and logic functions for client and server runtime behavior.
Catalog installation shows requested capabilities before a user approves the package. The installed application keeps the approved grant. Front components that request camera or microphone access use a separate workspace-level media permission grant. A member who can manage applications must approve this grant. A failed save or a cancel leaves the grant unchanged. The grant can include only permissions that the manifest requested. An agent linked to an application role stays within that application's access boundary.
References: packages/…/compute-application-manifest-all-universal-flat-entity-maps.service.ts• L230-341 packages/…/application-capability.resolver.ts• L19-53 packages/…/application-iframe-media-permission.resolver.ts• L50-113 packages/…/application-iframe-media-permission.service.ts• L31-107 packages/…/manifestType.ts• L41-70 packages/…/build-application-grant-role-from-to-flat-entity-maps.util.ts• L191-338
Standard application baseline
The standard application is the engine-owned baseline for every workspace. It supplies the core workspace model and user experience. Treat it as platform state when reasoning about a catalog application. It is not a public package that a workspace can export, install, or remove.
References: packages/…/twenty-standard-application.service.ts• L36-134 packages/…/assert-flat-application-is-exportable.util.ts• L16-45
Public application catalog
Catalog registration
The public catalog is the instance-wide view of packages that users can install. A catalog registration is not a workspace installation. It holds shared identity and display data while each workspace keeps its own installed version, configuration, capability grant, and state.
Catalog synchronization resolves package versions and checks package identity, manifest data, dependency information, and server compatibility before it creates or updates a registration. A package that fails these checks does not become an installed application.
The catalog also supports workspace-owned tarball packages. These packages stay unlisted and remain available to their owner. A direct share link can expose an unlisted package without making it a normal catalog choice. It can also show built-in catalog entries for products that connect to Twenty without being a normal packaged workspace installation. Public catalog queries return listed package registrations. Authenticated catalog queries can include these built-in entries.
References: packages/…/application-registration.service.ts• L646-775 packages/…/application-tarball.service.ts• L118-255 packages/…/application-dependency-files.service.ts• L31-87 packages/…/marketplace-query.service.ts• L48-95 packages/…/marketplace-public.resolver.ts• L23-47 packages/…/marketplace-built-in-applications.constant.ts• L7-56
Catalog review
The catalog helps a user decide whether a package fits the workspace before installation. It presents package identity, publisher details, content, support links, images, version information, declared access, configuration needs, and billing behavior.
The available application page separates review into three views:
- About describes the package and its publisher.
- Content previews the data, layout, logic, workflow, intelligence, access, and connection features in the manifest.
- Permissions shows the default role and requested capabilities before authorization.
Detailed catalog data also exposes requested media access, whether the package bills credits, install count, role access, object summaries, and explicit content summaries. This lets review cover both workspace features and sensitive runtime access before approval.
Ownership is separate from installation. One publisher can own a catalog registration while many workspaces install it. A publisher can also claim an unowned registration after it proves ownership.
The catalog-to-workspace path is:
flowchart LR
Registry[Package source] --> Resolve[Resolve package version]
Resolve --> Validate[Validate package and manifest]
Validate --> Registration[Catalog registration]
Registration --> Review[Review content and permissions]
Review --> Install[Approve workspace install]
Install --> Application[Installed application]
References: packages/…/marketplace-query.service.ts• L98-237 packages/…/marketplace-app-detail.dto.ts• L23-155 packages/…/marketplace-public.resolver.ts• L23-47 packages/…/marketplace.resolver.ts• L48-100
Packaged runtime capabilities
Logic functions and jobs
A logic function is a packaged server action. Its manifest entry links a stable function identity to the delivered handler and describes the event or request that starts it.
Logic functions support these product actions:
- HTTP routes, scheduled work, and data-event reactions.
- Tools and workflow actions.
- Health checks for configured applications.
- Install, update, connection, messaging, and uninstall work.
Packaged applications can run a built handler when the package provides its build checksum. Local development can use a live handler instead. Long work can run as an application job. A job keeps application, workspace, and optional member context while it runs outside the request that started it. Logic-function runs and lifecycle actions produce application-level health and usage signals.
Database-event settings can describe a workspace object or every object, an action, watched fields, a condition, and batch behavior. The sync resolves those references before it stores the event settings. A relation can be watched only when the platform has a single-record join field that can receive the event.
References: packages/…/logicFunctionManifestType.ts• L8-43 packages/…/from-logic-function-manifest-to-universal-flat-logic-function.util.ts• L19-114 packages/…/compute-application-manifest-all-universal-flat-entity-maps.service.ts• L238-275 packages/…/resolve-database-event-trigger-manifest-settings-or-throw.util.ts• L1-214 packages/…/application-install.service.ts• L519-703
Front components and commands
A front component is a packaged user interface unit. It can render a screen, a page-layout widget, a settings surface, or a headless client behavior inside the application shell. A command menu item can expose the component as a user action.
The host gives a component an application access token and the current context. That context can include the member, selected records or a record filter, object metadata, activity data, the current location, locale, color scheme, or an AI tool call. The host bridge lets the component navigate, open a panel, show a message, report command progress, refresh its token, upload a non-empty file to a file field, and keep application-and-member-scoped device data.
The platform exposes built component resources only through an application-reachable path. The host can return a temporary resource URL or stream the built resource. A missing or failed resource produces an unavailable component state rather than partial code. Shared front-end resources use checksums. A checksum change signals installed components to refresh. Media access remains subject to the application's approved workspace grant.
References: packages/…/frontComponentManifestType.ts• L9-44 packages/…/useFrontComponentExecutionContext.ts• L126-149 packages/…/useFrontComponentExecutionContext.ts• L459-653 packages/…/application-front-component-source.service.ts• L26-80 packages/…/front-component.controller.ts• L40-127 packages/…/application-sync.service.ts• L298-345
Data model, views, and page layouts
An application can define new business objects or extend objects already in the workspace. Fields describe the data and its links. Views, page layouts, related record paths, and validation rules turn that model into a usable and safe workspace experience. Local workspace choices stay separate from the package definition.
The manifest keeps object and field links explicit. Relation fields must name their target object and field. Related record paths describe the field chain used to reach records through one or more links. Validation rules name an object and an expression. The sync checks that expression against available fields. A rule can remain inactive when a workspace deactivates a field. A rule that loses an application-owned field cannot be silently restored.
The manifest can also add navigation, settings items, commands, timeline activity types, roles, and permission rules. These features connect the data model to the workspace shell without making the package own unrelated workspace state. Export preserves supported view-field settings and navigation links by their universal identifiers.
References: packages/…/compute-application-manifest-all-universal-flat-entity-maps.service.ts• L95-228 packages/…/compute-application-manifest-all-universal-flat-entity-maps.service.ts• L554-833 packages/…/from-flat-view-field-to-view-field-manifest.util.ts• L6-33 packages/…/from-navigation-menu-item-manifest-to-universal-flat-navigation-menu-item.util.ts• L8-45 packages/…/from-flat-navigation-menu-item-to-navigation-menu-item-manifest.util.ts• L6-52 packages/…/add-validation-rule-manifests-to-flat-entity-maps-or-throw.util.ts• L577-673
Workflows and connected accounts
An application workflow is packaged automation with one supported trigger and a graph of typed steps. Supported triggers include manual launch, schedules, database events, and webhooks. Steps can use application logic, AI agents, records, forms, filters, branches, and workspace connected accounts. The broader execution model is described in workflow execution.
The sync resolves application objects, fields, functions, agents, roles, and connected accounts before it creates the active workflow. Stable workflow and version identifiers link the same workflow across package updates. Schedule triggers become active cron entries after a successful sync. Manual triggers can become command menu actions. Database-event triggers can target an application object or a workspace object and can check watched fields or a condition.
Workflow export includes an active published version when the stored workflow can be reproduced by a manifest. It converts stored record, field, logic-function, agent, and shared-account references back to package identifiers. Unsupported steps or references are reported in export coverage instead of being silently presented as portable package content.
The package form and the workspace form use different identifiers for the same references. Apply resolves manifest identifiers into workspace records. Export reverses that mapping and omits values that the platform can derive from defaults. This keeps a package stable when workspace record IDs differ.
References: packages/…/application-manifest-migration.service.ts• L235-388 packages/…/from-workflow-manifest-to-universal-flat-workflow-or-throw.util.ts• L60-160 packages/…/from-workflow-step-manifest-to-action-or-throw.util.ts• L15-238 packages/…/from-workflow-trigger-manifest-to-trigger-or-throw.util.ts• L74-262 packages/…/build-database-event-trigger-manifest-lookup.util.ts• L1-38
Connections and messaging
A connection provider gives an application a controlled way to link an external account to a workspace. It can use standard OAuth, OAuth discovery, or an application-defined flow. The resulting connected account holds the account identity and protected credentials used by the application.
An application-defined flow uses packaged logic functions for authorization and callback work. Providers can also name logic functions that identify an account or run after connect and disconnect. Provider scope controls whether the resulting account is shared with the workspace or tied to a member. API-key providers can use an application-defined connection flow without OAuth.
A messaging provider uses one of those connection providers and links the external account to a send-message action. It can add channels, folders, and outbound message behavior while the platform keeps account access and message state inside the application boundary. This is the packaged form of the broader connected accounts and messaging model.
An application can also declare an MCP server. The server names a remote tool endpoint and can point to an application-owned connection provider. This lets packaged workflows and tools reach an external service without moving account ownership out of the application model.
References: packages/…/connectionProviderManifestType.ts• L7-26 packages/…/messagingProviderManifestType.ts• L4-11 packages/…/mcpServerManifestType.ts• L3-8 packages/…/from-connection-provider-manifest-to-universal-flat-connection-provider.util.ts• L28-88 packages/…/connection-provider-custom-flow.service.ts• L45-184 packages/…/from-mcp-server-manifest-to-universal-flat-mcp-server.util.ts• L5-24
Agents and skills
Applications can declare agents and skills as workspace capabilities. An agent runs with a workspace member context and can receive a prompt or message history with file attachments. Skills provide reusable instructions or behavior that an agent can use.
An agent can be linked to an application role. That link keeps agent use inside the application's access boundary. Export includes only agents and skills that the manifest can reproduce. Unsupported links or state appear in export coverage.
References: packages/…/compute-application-manifest-all-universal-flat-entity-maps.service.ts• L500-551 packages/…/from-agent-manifest-to-universal-flat-role-target.util.ts• L5-31 packages/…/reconstruct-agents-manifest.util.ts• L17-191 packages/…/reconstruct-skills-manifest.util.ts• L31-66
Workspace synchronization
Manifest application
Manifest application turns the package description into a workspace migration. The system compares the incoming package state with the current application-owned state. It then creates, updates, or removes only the entities that the manifest can express.
The shared apply path serves catalog installs, tarball installs, and local development sync. It can compute a dry-run plan before changing the workspace. The manifest is translated into application-owned workspace entities with stable links between objects, fields, permissions, agents, layouts, workflows, validation rules, and related record paths. After a successful schema change, the system can generate the application's SDK client. It also refreshes application references such as the default role, settings component, health check, and uninstall action.
Manifest omission is not a request to delete workspace-local state when the sync is partial. Uninstall is different. It explicitly removes the application's tracked metadata and its dependents. Connected accounts are cleaned up before a removed connection provider is released. Schedule-trigger cache entries are published after metadata changes. Translation sync is non-critical and can repair itself on a later sync.
References: packages/…/application-manifest-apply.service.ts• L17-100 packages/…/application-sync.service.ts• L67-153 packages/…/application-manifest-migration.service.ts• L183-388 packages/…/application-development.service.ts• L129-209
Installed content summaries
Installed application content is the workspace view of what one application owns. It gives catalog and settings surfaces a compact summary of data, layout, navigation, runtime, access, connection, asset, and translation capabilities without exposing unrelated workspace state.
The summary uses application ownership and stable identifiers to group related items. It leaves out soft-deleted records, system-owned records, personal views and navigation items, and private agents. It reports useful labels, types, published workflow status, trigger tags, and child counts so a person can understand the installed product before opening each feature.
The installed content service combines this owned workspace summary with the application's public assets and translations. This keeps the content shown for an installed application tied to the current workspace state while the catalog can still preview content from the package manifest.
References: packages/…/build-application-content-from-flat-entity-maps.util.ts• L14-61 packages/…/build-application-content-from-flat-entity-maps.util.ts• L63-179 packages/…/build-application-content-from-flat-entity-maps.util.ts• L212-413 packages/…/application-content.service.ts• L31-72 packages/…/application-content.dto.ts• L5-63
Local development and export
The SDK gives application authors a plan-then-apply workflow. A plan shows workspace changes without applying them. An apply syncs the local manifest and package files after version and ownership checks. Missing entities are inferred as deletions only when the sync has a complete target description; local custom application pulls can avoid that inference. See application CLI for the author workflow.
Export turns supported application-owned workspace state into a portable manifest. It reconstructs data, roles, views, layouts, navigation, related record paths, workflows, agents, skills, validation rules, translations, and selected public assets. Optional dependency files, front-component source files, source dependencies, and public assets are returned with coverage entries that state whether each item was exported, excluded, or unsupported.
Source inventories tie front-component source files to the deployed component path and build checksum. Export shares a 12 MiB encoded file budget across dependency files, front-component sources, source dependencies, and public assets. Files that do not fit remain in export coverage instead of making the rest of the export look complete.
Only local applications are exportable. Published package installations, tarball installations, OAuth-only registrations, and the standard application stay tied to their source or the platform. They must use their supported install or recreation path instead. A workflow must have an active published version and resolvable references. Workspace state that a manifest cannot express remains outside the portable package. Public asset export is optional and can report assets that do not fit the export budget as unsupported.
The development and export path is:
flowchart LR
Workspace[Workspace application state] --> Plan[Build plan or export]
Plan --> Coverage[Resolve supported and unsupported state]
Coverage --> Manifest[Portable manifest]
Coverage --> Files[Optional package files]
Manifest --> Apply[Apply to a local application]
Files --> Apply
References: packages/…/application-development.service.ts• L104-209 packages/…/application-export.resolver.ts• L45-74 packages/…/application-manifest-export.service.ts• L65-330 packages/…/application-front-component-export.service.ts• L33-167 packages/…/application-front-component-source.service.ts• L83-221 packages/…/application-public-asset-export.service.ts• L33-111 packages/…/application-export-file-budget-bytes.constant.ts• L1
Application lifecycle
Installation and upgrades
Installation resolves one package version, checks server compatibility and package integrity, stores package resources, applies the manifest, and runs declared lifecycle actions. A pre-install action can be made available before the full manifest sync. A post-install action can run as part of the operation or as later work.
Install, upgrade, and uninstall requests return a job identifier. A workspace queue performs the long operation and reports progress. A shared workspace-and-application lock prevents duplicate or opposite lifecycle operations from changing the same application at the same time.
An upgrade uses the same path with a newer compatible package version. Automatic rollout skips applications that are current, have automatic updates disabled, are not on a provisioned workspace, or do not meet the server version requirement. Lifecycle outcomes record the operation, package version, and safe error information for support and monitoring. A failed fresh install removes the incomplete application state. A failed upgrade keeps the existing installed application. Local development and OAuth-only registrations do not run the packaged install path because they have no catalog package artifacts to install.
The main asynchronous boundary is:
sequenceDiagram
participant User as Workspace user
participant API as Application API
participant Queue as Workspace queue
participant App as Installed application
User->>API: Request install, upgrade, or uninstall
API-->>User: Return job identifier
API->>Queue: Enqueue workspace/application job
Queue->>App: Apply lifecycle operation
Queue-->>User: Broadcast progress and final state
References: packages/…/application-install.service.ts• L102-228 packages/…/application-install.service.ts• L264-351 packages/…/application-install.service.ts• L355-619 packages/…/application-install.service.ts• L622-858 packages/…/application-install.module.ts• L51-67
Authorization and application targeting
OAuth lets an external client request access to an installed application for a member or for the application itself. The flow checks the client, redirect, proof key or secret, workspace membership, and requested scope before it returns tokens.
An authorization code can install the registered application in the target workspace when no installation exists. This connects external authorization to the same package and lifecycle model as a catalog install. Application-targeted requests accept a supported application identifier and verify the target before the handler runs.
The platform records active member authorizations per workspace and application. Members can review and revoke their own grants. A member with application-management access can review and revoke active grants for the whole workspace. The record keeps the approved scopes when known, the last authorization time, and the last use time. Older refresh-token grants can remain identifiable even when they have no stored consent scope or consent time.
References: packages/…/application-registration.resolver.ts• L102-223 packages/…/application-registration.resolver.ts• L253-309 packages/…/application-install.module.ts• L47-60 packages/…/application-authorization.service.ts• L16-205 packages/…/application-authorization.resolver.ts• L17-68 packages/…/workspace-application-authorization.resolver.ts• L17-65 packages/…/application-authorization.dto.ts• L5-41
Uninstallation
Uninstallation removes the application's workspace capabilities as a tracked operation. If the package declares uninstall behavior, that action runs first so the application can clean up state that the manifest cannot describe.
The removal path deletes application-owned metadata, related dependents, package records, stored files, and runtime resources. A non-removable application is rejected before this work starts. Removing a connection provider also removes the connected accounts that depend on it.
An owner workspace cannot remove an application registration that still provides a server route to other workspaces. Workspace deletion gives installed applications a chance to run cleanup. Final hard deletion continues on a best-effort basis even when an application hook fails.
References: packages/…/application-sync.service.ts• L350-505 packages/…/application-manifest-migration.service.ts• L312-353 packages/…/application-uninstall-runner.service.ts• L36-117
Installed application settings
Installed application settings are the operational view of a package inside one workspace. They separate catalog discovery from installed state and show the selected application's capabilities, versions, configuration, connections, support links, and lifecycle controls.
The settings view groups installed content into data, layout, and logic. It can show objects and fields, pages and views, navigation, components and commands, logic functions, workflows, agents, skills, roles, connections, messaging providers, MCP servers, activity types, and validation rules. Missing required values appear as a configuration prompt. A health check can return a status, message, and safe in-workspace action. A stopped application shows degraded behavior.
An application can replace the standard variables tab with a settings front component. Connection setup links to connected accounts and messaging. Broader client-side extension behavior belongs with extension integrations.
References: packages/…/useApplicationsWithPreferences.ts• L1-80 packages/…/SettingsApplicationDetails.tsx• L161-365 packages/…/getApplicationHealthBanner.ts• L17-55 packages/…/SettingsApplicationDetailVariablesTab.tsx• L23-97
Application monitoring
Application monitoring gives publishers and instance operators a product-level view of packaged behavior. It combines runtime activity, lifecycle results, issues, version spread, function performance, rate-limit events, and credit use over a selected time range.
Publishers can view monitoring for registrations they own. Instance admins can also view workspace counts and workspace-level results. The view links failures to package versions and logic functions so operators can compare behavior across installations without inspecting package code.
References: packages/…/application-monitoring.service.ts• L64-119 packages/…/application-monitoring.dto.ts• L106-152 packages/…/application-monitoring.resolver.ts• L32-65 packages/…/admin-application-monitoring.resolver.ts• L41-59
Change checklist
When these files or sections are changed, remember to consider these:
- Keep manifest types, manifest validation, manifest-to-workspace conversion, workspace sync, and export conversion aligned when a new package capability is added.
- Preserve universal identifiers and cross-manifest references when changing data, roles, workflows, validation rules, functions, components, connections, messaging, agents, skills, related record paths, or MCP servers.
- When changing application content summaries, keep application ownership, soft-delete filtering, personal-state filtering, labels, relationship counts, and the content DTO aligned with catalog and settings consumers.
- When changing dependency or built-resource declarations, keep manifest paths, stored files, checksums, package loading, and shared front-end resources aligned.
- When changing front-component source inventories, keep the source path, source checksums, deployed build checksum, stored inventory, and export file budget aligned.
- When changing workflow manifests, review trigger support, connected-account selection, reference resolution, active version handling, cron cache entries, and export coverage together.
- When changing database-event trigger settings, keep object and field lookup priority, watched-field rules, condition bindings, stored event settings, logic functions, agents, and workflow triggers aligned.
- When changing application configuration, keep types, required and deprecated state, secret handling, scopes, defaults, and settings views on the same contract.
- When changing front-component resources or host actions, preserve token access, context, resource access, storage namespaces, checksum updates, file-field checks, and media permission approval.
- When changing front-component upload or media flows, preserve non-empty file checks, FILES-field targeting, workspace-manager authorization, retry behavior, and abort handling.
- When changing install or update behavior, preserve package identity checks, server compatibility, version ordering, pre-install and post-install actions, SDK generation, rollback, queue status, and lifecycle records.
- When changing uninstall behavior, review connection cleanup, dependent metadata removal, runtime resource cleanup, route ownership, and workspace deletion behavior together.
- When changing export behavior, keep source eligibility, entity reconstruction, reference resolution, public asset inclusion, file budget accounting, and coverage statuses aligned. Check validation rules, related record paths, and active workflow versions with the other manifest entities.
- When changing local sync behavior, keep dry-run output, deletion inference, ownership checks, rate limits, application locks, registration metadata, and public asset copying aligned.
- When changing authorization behavior, keep consent scopes, member and workspace revocation boundaries, legacy refresh-token backfill, application identity, and OAuth token use aligned.
- When changing media permission behavior, keep manifest requests, catalog approval, workspace grants, front-component exposure, and browser use aligned.
- When changing shared package dependencies, update the package manifest and lock data as one versioned unit. Keep the standard and workspace-custom dependency sets distinct. The workspace-custom package includes shared front-end dependencies that must remain compatible with packaged front components.
Important failure modes
| Trigger | Consequence | Guard |
|---|---|---|
| Stored dependency files do not match the manifest checksums. | Manifest synchronization stops before runtime files are trusted. | Publish the dependency files and their declared checksums as one package version. |
| A required application variable has no value. | The application stays not configured and its health check is not a reliable readiness signal. | Fill all required values before relying on the application. |
| A manifest references a missing item or an item owned by another application. | Sync rejects the package before it changes workspace state. | Keep every reference valid and application-owned where the contract requires it. |
| A database-event trigger names an unknown object, a field from another object, or an inactive field. | The event settings cannot be resolved and sync fails. | Resolve event objects and fields against the application-first lookup and validate conditions before publish. |
| A relation trigger watches a relation to many records or a relation without a join field. | The trigger cannot identify one changed field and is rejected. | Watch scalar fields or single-record relation fields only. |
| A relation field omits its target object or field. | The data model cannot be applied. | Keep both relation target identifiers in the manifest. |
| A validation rule uses an invalid expression or an application-owned field that the manifest removed. | The application sync fails instead of creating a rule that cannot run. | Compile rule expressions against the post-sync data model and update the rule with its field changes. |
| A related record path points to an unsupported or unreproducible field chain. | The path is left out of export and appears in export coverage as unsupported. | Use a field chain that the manifest can express and review coverage after export. |
| A workflow uses an unsupported step or cannot resolve its object, field, role, function, agent, or connected account. | The workflow is not created or activated. | Use supported step shapes and provide a valid shared workspace account for account steps. |
| A workflow schedule is invalid or a database-event watched field cannot be mapped. | The workflow cannot be created from the manifest. | Use a valid schedule and watch only supported fields on the trigger object. |
| A package update omits application metadata during a full sync. | Application-owned items can be removed. | Use partial sync for incomplete descriptions and full sync only for a complete target state. |
| A local pull infers deletions from an incomplete application description. | Workspace capabilities that are not in the pull can be removed. | Use dry run first and disable deletion inference for incomplete local pulls. |
| A front component cannot load its component, token, or shared resources. | The host shows an unavailable state instead of a partial component. | Keep component resources, access checks, checksums, token access, and application ownership aligned. |
| A stored front-component source inventory does not match the deployed path or build checksum. | Source export is rejected as stale. | Apply or publish the application again before exporting source files. |
| Front-component sources or public assets exceed the shared export budget. | Those files are marked unsupported while the rest of the export can continue. | Review coverage and keep the encoded export under the 12 MiB budget. |
| A front component sends an empty value or targets a non-FILES field for upload. | The host rejects the upload before it can create an unattached file. | Send a non-empty blob and a valid FILES field identifier. |
| Approved media permissions are not in the manifest request. | Approval is rejected and the application does not receive the new media grant. | Review the current request and approve only its intersection with the requested permissions. |
| A member without application-management permission requests media access, or saving the grant fails. | No workspace grant is created and the front component stays without access. | Use an authorized member and retry after the save error. Cancelled requests must remain unresolved. |
| An install, upgrade, or uninstall starts while an opposite lifecycle job is active. | The new operation is rejected. | Use the returned job status and wait for the current operation to finish. |
| A removed connection provider still has connected accounts. | Sync must clean up those accounts before it can complete. | Validate the migration and remove accounts through the provider cleanup path. |
| An owner workspace removes a route application that other workspaces use. | Registration removal is denied to protect those routes. | Remove dependent installations or transfer ownership first. |
| An export contains private, changed, or unsupported workspace state. | The exported package cannot reproduce all of the source state. | Read export coverage and treat unsupported entries as workspace-only state. |
| A member revokes an authorization outside the member's workspace or another member's grant. | The authorization remains active because the revoke criteria do not match it. | Revoke through the member or workspace operation that owns the grant. |
| A public catalog request targets an unlisted registration. | The catalog does not return it as a public application. | Publish the registration or use its owner-controlled share path. |
| Installed content is built from stale or incomplete workspace cache data. | Catalog or settings content can omit current application items or show outdated counts. | Recompute the workspace cache for the content maps before returning the installed content summary. |
| Personal or soft-deleted workspace records are treated as application content. | Private user state or removed items appear in the installed application's public summary. | Apply application ownership and content filters before building the content DTO. |
Key files
| File | Why to read it |
|---|---|
| packages/…/manifestType.ts | Shows the top-level package contract and capability groups. |
| packages/…/applicationType.ts | Shows application identity, configuration, lifecycle hooks, capability requests, and resource checksums. |
| packages/…/roleManifestType.ts | Shows role access as records permissions with support for older role manifests. |
| packages/…/mcpServerManifestType.ts | Shows how a package declares a remote tool server and its optional connection provider. |
| packages/…/application-manifest-apply.service.ts | Shows the shared apply path for catalog, tarball, and local manifest sync. |
| packages/…/application-manifest-migration.service.ts | Shows how a manifest becomes a checked workspace migration, including database-event triggers, validation rules, workflows, and connected-account cleanup. |
| packages/…/application-sync.service.ts | Shows package verification, application state sync, uninstall, capability grants, media grants, and runtime cleanup. |
| packages/…/compute-application-manifest-all-universal-flat-entity-maps.service.ts | Shows the broad set of workspace capabilities a manifest can describe and how event settings are resolved. |
| packages/…/application-content.service.ts | Shows how installed application summaries combine owned workspace content with public assets and translations. |
| packages/…/build-application-content-from-flat-entity-maps.util.ts | Shows which application-owned workspace items appear in the installed content summary and which private or removed items are excluded. |
| packages/…/application-content.dto.ts | Defines the content summary shape shared by installed application and catalog views. |
| packages/…/application-manifest-export.service.ts | Shows how supported workspace application state becomes a portable export. |
| packages/…/application-front-component-export.service.ts | Shows how front-component definitions and source files enter an export. |
| packages/…/application-front-component-source.service.ts | Shows how deployed front-component source inventories are checked and restored. |
| packages/…/application-public-asset-export.service.ts | Shows how selected public assets enter an export and how unsupported files are reported. |
| packages/…/application-export-file-budget-bytes.constant.ts | Defines the shared encoded file budget for exports. |
| packages/…/reconstruct-workflows-manifest.util.ts | Shows which workflow state can become package content. |
| packages/…/reconstruct-validation-rules-manifest.util.ts | Shows how validation rules become package content and how unsupported rules are reported. |
| packages/…/reconstruct-related-record-paths-manifest.util.ts | Shows how related record paths are exported and how unsupported paths are reported. |
| packages/…/application-development.service.ts | Shows local application creation, dry-run sync, deletion inference, and export entry points. |
| packages/…/application-export.resolver.ts | Shows the protected workspace export interface and optional file controls. |
| packages/…/application-dependency-files.service.ts | Shows how package dependency files are read and verified. |
| packages/…/build-application-file-list.util.ts | Shows the package resources stored for logic functions, front components, shared dependencies, source files, and public assets. |
| packages/…/application-install.service.ts | Shows the high-level install, update, capability, media permission, queue, rollback, and lifecycle flow. |
| packages/…/application-uninstall-runner.service.ts | Shows the locked uninstall boundary and lifecycle outcome recording. |
| packages/…/application-iframe-media-permission.service.ts | Shows how requested media permissions are read and approved for an installed application. |
| packages/…/application-registration.service.ts | Shows catalog registration, ownership, publication, version protection, and install statistics. |
| packages/…/marketplace-query.service.ts | Shows public and authenticated catalog views, built-in entries, review data, and permission summaries. |
| packages/…/marketplace-public.resolver.ts | Shows the public boundary for listed marketplace applications. |
| packages/…/application-authorization.service.ts | Shows how active application grants are recorded, listed, touched, backfilled, and revoked. |
| packages/…/application-authorization.resolver.ts | Shows member-level authorization review and revocation. |
| packages/…/workspace-application-authorization.resolver.ts | Shows workspace-level authorization review and revocation. |
| packages/…/connection-provider-custom-flow.service.ts | Shows the custom external-account authorization and callback flow. |
| packages/…/application-monitoring.service.ts | Shows publisher and admin monitoring across runs, lifecycle events, versions, functions, and usage. |
| packages/…/front-component.controller.ts | Shows how a packaged front component's built resource is safely exposed to its host. |
| packages/…/front-component.resolver.ts | Shows front-component reachability, application tokens, public variables, capability grants, and media grants. |
| packages/…/useFrontComponentExecutionContext.ts | Shows the context and host actions exposed to packaged front components. |
| packages/…/isNonEmptyBlob.ts | Shows the input guard for file uploads from packaged front components. |
| packages/…/SettingsApplicationDetails.tsx | Shows installed application configuration, health, content, updates, authorization, and removal. |
| packages/…/package.json | Shows the separate dependency set and shared front-end resources for workspace-custom applications. |
| packages/…/twenty-standard-application.service.ts | Shows the engine-owned baseline that is not a public installed package. |