--- title: "Application Dependencies" slug: "application-dependencies" status: "update" updated: 2026-10-13T15:32:15Z published: 2026-10-13T15:32:15Z canonical: "docs.unqork.io/application-dependencies" --- > ## 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. # Application Dependencies When one versioned application uses modules from another versioned application, the second application must be set as a dependency of the first. Dependencies ensure that both applications use compatible, versioned states of each other. ## What Defines a Dependency The following module relationships create a dependency between applications: - Imported modules (direct and nested) - Module executions - Workflow hand-offs - Submission references - Dynamic Refresh configurations - Header and footer modules - Login and logout modules - Transforms When versioning is enabled on an application that already has these relationships, the platform detects and adds the dependencies automatically. ### What Is Not Included The following elements are excluded from versioning and do not create dependencies: - **Data Collections**: The data stored in each environment is not versioned — only the structure and logic are versioned. - **Managed Assets**: These include PDFs, images, and CSS files. - **Environment Configurations**: These include integrations, RBAC policies, and SSO settings. - **External Services**: References to external APIs are versioned, but the external services themselves are not. ## Open the Manage Dependencies Dialog To open the Manage Dependencies dialog: 1. In the module toolbar, click the checkout pill. ![Module Builder tab bar showing the checkout pill displaying the current branch name.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/api_upload_20261013_153214_158779edf74a4d698ddbd395c992ddc1.png?sv=2026-02-06&spr=https&st=2026-11-02T07%3A17%3A11Z&se=2026-11-02T08%3A17%3A11Z&sr=c&sp=r&sig=MiTNTtALONLtbpi4Dyzzc5nZYIN89wvBEjq9Tu9MBTg%3D) 2. Hover ![GitBranch](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/api_upload_20261013_153214_ed2432ed9a674fef9405cd205d4945b3.svg?sv=2026-02-06&spr=https&st=2026-11-02T07%3A17%3A11Z&se=2026-11-02T08%3A17%3A11Z&sr=c&sp=r&sig=MiTNTtALONLtbpi4Dyzzc5nZYIN89wvBEjq9Tu9MBTg%3D) **Versioned Actions**, then select ![Layers](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/api_upload_20261013_153214_91daf52d3bc74cf5a366894ef2dec170.svg?sv=2026-02-06&spr=https&st=2026-11-02T07%3A17%3A11Z&se=2026-11-02T08%3A17%3A11Z&sr=c&sp=r&sig=MiTNTtALONLtbpi4Dyzzc5nZYIN89wvBEjq9Tu9MBTg%3D) **Manage Dependencies**. > [!WARNING] > **Manage Dependencies** is only available for versioned applications and requires update permission. The dialog is read-only when viewing a published version. Switch to a branch to make changes. ## Manage Dependencies Dialog The dialog lists all applications that the current application depends on. Use the search field to filter by name. Each row shows the application name and the version currently set as the dependency. Click the ![EllipsisVertical](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/api_upload_20261013_153214_25ba7adbcde74202ad0ebc3a9b7834b9.svg?sv=2026-02-06&spr=https&st=2026-11-02T07%3A17%3A11Z&se=2026-11-02T08%3A17%3A11Z&sr=c&sp=r&sig=MiTNTtALONLtbpi4Dyzzc5nZYIN89wvBEjq9Tu9MBTg%3D) (**ellipsis**) on a row to access **Change version** and **Remove**. ![Manage Dependencies dialog with a search field and a table listing dependent applications and their versions.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/api_upload_20261013_153214_e99b0849cc6149abbb9465675a1ce1e1.png?sv=2026-02-06&spr=https&st=2026-11-02T07%3A17%3A11Z&se=2026-11-02T08%3A17%3A11Z&sr=c&sp=r&sig=MiTNTtALONLtbpi4Dyzzc5nZYIN89wvBEjq9Tu9MBTg%3D) ## Add a Dependency To add a new dependency: 1. In the module toolbar, click the checkout pill, hover ![GitBranch](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/api_upload_20261013_153214_ed2432ed9a674fef9405cd205d4945b3.svg?sv=2026-02-06&spr=https&st=2026-11-02T07%3A17%3A11Z&se=2026-11-02T08%3A17%3A11Z&sr=c&sp=r&sig=MiTNTtALONLtbpi4Dyzzc5nZYIN89wvBEjq9Tu9MBTg%3D) **Versioned Actions**, then select ![Plus](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/api_upload_20261013_153214_25444d8e705e47d49279e73e9f4b1339.svg?sv=2026-02-06&spr=https&st=2026-11-02T07%3A17%3A11Z&se=2026-11-02T08%3A17%3A11Z&sr=c&sp=r&sig=MiTNTtALONLtbpi4Dyzzc5nZYIN89wvBEjq9Tu9MBTg%3D) **Add Dependencies**. 2. In the search field, type the name of the application to add. 3. Select the application from the results list. Applications with versioning enabled display a **Versioned** badge. 4. In the version picker, select the version to use as the dependency. 5. Click **Add Dependency**. The dependency displays in the list. If the application does not appear in results, it might not be published or might not have versioning enabled. ## Change a Dependency Version To change the version of an existing dependency: 1. In the Manage Dependencies dialog, click the ![EllipsisVertical](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/api_upload_20261013_153214_25ba7adbcde74202ad0ebc3a9b7834b9.svg?sv=2026-02-06&spr=https&st=2026-11-02T07%3A17%3A11Z&se=2026-11-02T08%3A17%3A11Z&sr=c&sp=r&sig=MiTNTtALONLtbpi4Dyzzc5nZYIN89wvBEjq9Tu9MBTg%3D) (**ellipsis**) on the dependency row. 2. Select ![Pencil](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/api_upload_20261013_153214_067346787cdd4104a26ed743ee9e71f4.svg?sv=2026-02-06&spr=https&st=2026-11-02T07%3A17%3A11Z&se=2026-11-02T08%3A17%3A11Z&sr=c&sp=r&sig=MiTNTtALONLtbpi4Dyzzc5nZYIN89wvBEjq9Tu9MBTg%3D) **Change version**. 3. In the version picker, select the new version. 4. Confirm the selection. A confirmation message displays. ## Remove a Dependency To remove a dependency: 1. In the Manage Dependencies dialog, click the ![EllipsisVertical](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/api_upload_20261013_153214_25ba7adbcde74202ad0ebc3a9b7834b9.svg?sv=2026-02-06&spr=https&st=2026-11-02T07%3A17%3A11Z&se=2026-11-02T08%3A17%3A11Z&sr=c&sp=r&sig=MiTNTtALONLtbpi4Dyzzc5nZYIN89wvBEjq9Tu9MBTg%3D) (**ellipsis**) on the dependency row. 2. Select ![Trash2](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/api_upload_20261013_153214_373112fdce764ce6991374e1f2c3f11e.svg?sv=2026-02-06&spr=https&st=2026-11-02T07%3A17%3A11Z&se=2026-11-02T08%3A17%3A11Z&sr=c&sp=r&sig=MiTNTtALONLtbpi4Dyzzc5nZYIN89wvBEjq9Tu9MBTg%3D) **Remove**. 3. In the confirmation dialog, click **Remove** to confirm. The dependency is removed immediately. If the removal fails, an error message displays with details. --- **Changelog** | Date | Change | | --- | --- | | 2026-09-09 | Updated for the checkout pill's Versioned Actions fly-out. | | 2026-07-17 | Added Dependencies page image and inline icons; editorial pass. | | 2026-07-15 | Initial publication. | Elements are are what you use to build Unqork applications. Elements include modules, workflows, Data Collections, Data Schema, and Record Collections. Cascading Style Sheets (CSS) is a style sheet language used for presenting how a HTML or XML document looks to end-users. 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. Single Sign-On is an authentication scheme that enables users to use one set of login credentials across multiple services. 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.