--- title: "Application Dependencies Dashboard Tool" slug: "application-dependencies-dashboard-tool" description: "Explore the Application Dependencies Dashboard tool to visualize module relationships, access requirements, and filter dependencies for efficient project management." updated: 2026-04-27T17:19:50Z published: 2026-04-27T17:19:50Z canonical: "docs.unqork.io/application-dependencies-dashboard-tool" --- > ## 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 Dashboard Tool Creators must have specific role permissions in either [Environment Role RBAC](https://docs.unqork.io/docs/creator-role-administration) (role-based access control) or [WSRBAC](https://docs.unqork.io/docs/workspaces-role-based-access-control-wsrbac) (Workspaces Role-Based Access Control) to access the Application Dependencies Dashboard tool. Module dependencies may include scenarios like the following: - One module executes a remote call to another module. - A module retrieving submission data from a schema module. - A Creator importing one module into the [Panel](/v1/docs/panel-component) component of another module. ## Access Requirements Access to the Application Dependencies Dashboard tool requires holding specific role permissions in either [Environment Role RBAC](https://docs.unqork.io/docs/creator-role-administration) (Role-Based Access Control) or [WSRBAC](https://docs.unqork.io/docs/workspaces-role-based-access-control-wsrbac) (Workspaces Role-Based Access Control). - If using Environment Roles (not using WSRBAC), Creators with the appropriate role can view all data available in the dashboard. - If using WSRBAC: - Creators can view data related to modules and workflows in workspaces where they have access. - If a Creator cannot view certain data, it typically indicates that they do not have access to the workspace containing the relevant module. **Navgiating the Dashboard** To access the Application Dependencies Dashboard tool, navigate to your environment, click **Resources,** and select **UDLC Toolkit**: ![A static image displaying the Resources section of the UDesigner to access the UDLC Toolkit.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/UDLC in Resources.png?sv=2026-02-06&spr=https&st=2026-11-04T17%3A56%3A02Z&se=2026-11-04T18%3A56%3A02Z&sr=c&sp=r&sig=obRjWpsqtGE%2FxWgsfKBX3Co%2FI14OFq22djfRxDW%2Fh2A%3D) Under the **Plan and Design** section of the UDLC Toolkit, locate the **Application Dependencies** tool and click the **Use this tool** button: ![A static image displaying the Application Dependencies tool's Use this tool button in the UDLC Toolkit.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Application Dependencies - Use this tool.png?sv=2026-02-06&spr=https&st=2026-11-04T17%3A56%3A02Z&se=2026-11-04T18%3A56%3A02Z&sr=c&sp=r&sig=obRjWpsqtGE%2FxWgsfKBX3Co%2FI14OFq22djfRxDW%2Fh2A%3D) The Application Dependencies tool displays the dependencies between all modules in your environment. ![A static image displaying the configuration of the Application Dependencies tool.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Application Dependencies- configuration.png?sv=2026-02-06&spr=https&st=2026-11-04T17%3A56%3A02Z&se=2026-11-04T18%3A56%3A02Z&sr=c&sp=r&sig=obRjWpsqtGE%2FxWgsfKBX3Co%2FI14OFq22djfRxDW%2Fh2A%3D) To view dependent modules, open the Application Dependencies Dashboard tool in your environment. Search for a single module ID or filter across multiple workspaces. Modules configured using best practices display on the dashboard. The first two columns display the module ID and title of the non-dependent module. The next two columns display the module ID and title of the dependent module. The far right column displays the relationship type between the two modules. Relationship types include: - **Execute**: When a module performs a remote execute using another module. - **Import**: When a module imports another module. By default, the table displays the first 10 dependencies. Use the pagination buttons below the table to view more entries. **Filtering the Dashboard** Your environment may contain many application modules. The dashboard includes built-in filters to help you locate specific ones. Use some or all the filters at the same time, depending on how narrow you want the results. Filter by either module in the dependency relationship, for modules that import another module, or for modules performing a remote execute with another module. As you enter text into the fields, matches display automatically. Let's examine the dashboard's filters: | Filter | Description | | --- | --- | | Module ID | Filter by the module ID of the module dependent on the other. | | Module Title | Filter by the module title of the module dependent on the other. | | Dependency ID | Filter by the module ID of a module that another module depends on. > [!NOTE] > This module could be one imported into another module or a schema module you retrieve data from. | | Dependency Title | Filter by the module title of a module that another module depends on. > [!NOTE] > This module could be one imported into another module or a schema module you retrieve data from. | | Type | Filter by the dependency between the two modules. Select either **Execute** or **Import**. | Also known as Unqork Users, or Designer Users; is anyone who is inside the Unqork platform. 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. 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. WSRBAC (Workspaces Role-Based Access Control) is a method to control user access to a workspace. Users must be assigned to a workspace using WSRBAC before they can view or edit applications and modules inside the space. 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 Record Data. Submission data consists of information saved by Unqork components. View submission data by using the angular command, or in Record Collections. Schema is a declarative language that defines the structure, content, and constraints of the data. Also known as Unqork Users, or Designer Users; is anyone who is inside the Unqork platform. The UDLC (Unqork Development Lifecycle) Toolkit is a set of tools designed to manage Unqork applications. Pagination is the process of separating content into individual pages.