Dataphin:Restructure asset pages with custom menus

Background

The Dataphin Asset Catalog is a unified portal for searching and browsing various asset types, such as table, metric, API, and dashboard. Organizations often need to provide different asset consumption experiences for different business teams. For example:

• Providing a metric-only discovery entry point for business analysts.

• Embedding asset discovery capabilities into a custom company portal and removing redundant UI elements, such as the top navigation bar, to create a lightweight experience.

• Providing direct URL access to a simplified asset page that displays only the main search area.

To support these use cases, Dataphin provides three composable control layers: menu visibility control, tab access control, and URL parameters that hide page elements. This guide explains each capability and provides a complete configuration example.

Capability 1: Decouple asset permissions and control menu visibility

The permissions for a global role under Asset Catalog include five independent asset permissions: Display Menu, table, metric, API, and dashboard. You can configure these permissions for different roles in Management Center > Member Management > Global Role Management. For more details on permissions, see asset permissions.

This decoupling separates menu visibility from tab accessibility and provides the foundation for building custom asset operational pages.

Capability 2: Hide page elements with URL parameters

The Asset Catalog search page supports URL parameters that control which UI elements are displayed. These parameters allow you to embed a more streamlined interface in a custom menu or an external page. The following table lists the common parameters.

For example, the following URL opens the metric discovery page by default, with the asset tab bar and top navigation bar hidden: https://<your_domain>/market/catalog/search?activeTab=INDEX&search=&tenantId=<your_tenant_id>&assetTabHidden=true&topHidden=true.

Procedure

This topic uses Providing business analysts with an asset operations portal that supports only metric retrieval as an example to show how to combine three capabilities to complete the configuration.

Step 1: Prepare the asset page URL

Construct the URL for the Asset Catalog search page and append parameters to streamline the interface. For example: https://<your_domain>/market/catalog/search?activeTab=INDEX&search=&tenantId=<your_tenant_id>&assetTabHidden=true&topHidden=true.

• activeTab=INDEX: Opens the metric discovery page by default.

• assetTabHidden=true: Hides the asset tab bar so the page focuses only on metric content.

• topHidden=true: Hides the top navigation bar for a clean, embedded appearance.

• Use parameters such as tenantId as needed.

Step 2: Embed the page in a custom menu

1. In Management Center > System Settings > Tenant Settings > Style Settings, select the Menu Settings tab.

2. In the Asset Governance Management > Asset menu, click to add a first-level or second-level menu, such as Metric Catalog. In the new menu dialog box, enter the configuration information and click OK.

   In Menu Link URL, enter the URL that you prepared in Step 2, and turn off Show Top Navigation.

   Note

   After you save the custom menu, only super administrator and system administrator roles can view it by default. You must configure permissions for other roles in Global Role Management.

Step 3: Configure the custom role

1. In Management Center > Member Management > Global Role Management, edit an existing custom role or create a new custom global role (for example, business analyst).

2. In the Menu and Function Permission Configuration area, click Assets. The permissions under Assets-Catalog include Display Menu, Table, Metric, API, and Dashboard.

3. Select the permissions as needed (in this example, select only the Metric permission), and click OK to save the configuration.

   Deselect the Display Menu permission to hide the native Asset Catalog menu entry at the top and avoid duplication with the subsequent custom menu.

4. On the role editing page, select the custom menu you created in Step 2 to make it visible to this role.

5. Click OK to save the configuration.

Step 4: Verify the results

1. Log in to Dataphin with an account assigned to the target role.

2. Confirm that the native Asset Catalog menu is no longer visible in the top navigation bar. The new custom menu (Metric Catalog) appears instead.

3. Click the custom menu to open the embedded page. Confirm that the top navigation bar and asset tab bar are hidden, and only the main metric discovery area is displayed.

4. Confirm that you can only discover metric assets and that all other asset types are hidden.

   You have created a streamlined, focused, and role-specific asset operational page.

FAQ

• Q: If I clear the Display Menu permission, can users still access the Asset Catalog?

  A: Yes. The Display Menu permission only controls the visibility of the menu entry in the top navigation bar. It does not prevent users from accessing the Asset Catalog page via a direct URL. If a user opens the Asset Catalog page by using a direct URL, the menu entry is visible on that page. To control which asset types are actually accessible, use the specific permissions for table, metric, API, and dashboard.

• Q: What is the difference between the assetTabHidden parameter and the Display Menu permission?

  A: They operate at different levels. The Display Menu permission is a role-level setting that controls whether the menu entry in the top navigation bar is visible. The assetTabHidden parameter is a page-level URL parameter that controls whether the asset tab bar is visible on the Asset Catalog page. In a custom menu embedding scenario, you typically use them together: use the Display Menu permission to hide the native entry point and use the assetTabHidden parameter to streamline the embedded page.

• Q: Why should I also use the topHidden parameter?

  A: topHidden=true is used to hide the top navigation bar. When an asset page is embedded in a custom menu or an external portal, hiding the native top navigation bar avoids a repetitive page frame and makes the embedded page look more like a standalone lightweight application.