Edit, reorder, hide, or delete custom asset tabs to keep your Catalog organized and relevant to your users' needs.
After creating custom tabs, you can modify them to meet changing business needs. You can edit tab names and filter rules, reorder tabs to change their display sequence, hide tabs from users, or delete tabs that are no longer needed.
Your changes are applied immediately. All users in the workspace see the updated tab configuration in the Catalog.
Example: Editing a custom tab
To modify the "Production Assets" tab to also include staging assets:
- Go to .
- Click the "Production Assets" tab name to open the Edit Tab panel.
- Modify the filter rule: Change the Environment filter value from "Production" to include both "Production" and "Staging" using OR logic.
- Click Save.
The 'Production Assets' tab now displays assets.
After managing your tabs, you can:
- Create additional custom tabs to organize assets further. See create custom asset tabs.
- Monitor tab usage to ensure they remain relevant to your users' needs.
Filterable fields
When creating or editing custom tabs, you can filter assets by the following fields:
| Field name | Field type | Description |
|---|---|---|
| Asset Type ID | Object ID | The unique identifier of the asset type (for example, Datasource, Dataset, Field). |
| class | String | The asset class: Technical or Business. |
| Name | String | The name of the asset. |
| Description | String | The description of the asset. |
| Owner | String | The user or team that owns the asset. |
| Status | String | The status of the asset (for example, Active, Archived, In-review). |
| Environment | String | The environment where the asset resides (for example, Production, Staging, Development). |
| Created Date | Date | The date when the asset was created. |
| Custom properties | Varies | Any custom properties defined for the asset type (for example, Criticality). |
Filter operators
The following operators are available for filtering assets:
| Operator | Description |
|---|---|
| Equals | The field value exactly matches the specified value. |
| Not equals | The field value does not match the specified value. |
| In | The field value matches any value in the specified list. |
| Not in | The field value does not match any value in the specified list. |
| Contains | The field value contains the specified text (case-insensitive). |
| Not contains | The field value does not contain the specified text. |
| Starts with | The field value starts with the specified text. |
| Ends with | The field value ends with the specified text. |
| Greater than | The field value is greater than the specified value (for numeric and date fields). |
| Greater than or equal | The field value is greater than or equal to the specified value. |
| Less than | The field value is less than the specified value. |
| Less than or equal | The field value is less than or equal to the specified value. |
| Exists | The field has a value (is not empty). |
Filter logic
Custom tabs support flexible filter logic to create complex filtering scenarios:
- Match All (AND logic): All filter conditions must be true for an asset to appear in the tab. This is the default behavior. Use this when you want to narrow down results to assets that meet all your criteria.
- Match Any (OR logic): At least one filter condition must be true for an asset to appear in the tab. Use this when you want to broaden results to include assets that meet any of your criteria.
- Complex combinations: You can create complex filter scenarios by combining multiple filter groups with AND and OR logic.
Filter configuration examples
The following examples show how to configure filters for common use cases:
| Use case | Filter configuration |
|---|---|
| Show only production datasources | assetTypeId = Datasource AND Environment = Production |
| Show active or recently updated assets | Status = Active OR CreatedDate >= (last 30 days) |
| Show high-priority assets in specific domains | Criticality = High AND (Domain = Sales OR Domain = Finance) |
| Show assets owned by specific teams | Owner IN (DataEngineering, Analytics, DataGovernance) |
| Show assets with specific data classification | DataClassification = Confidential AND Status = Active |
| Show assets that contain specific text in name or description | Name CONTAINS "customer" OR Description CONTAINS "customer" |
Filter configuration best practices
- Use clear, descriptive tab names: Tab names should clearly indicate what assets the tab contains. For example, "Production Databases" is clearer than "Prod DB".
- Keep filters simple: Avoid overly complex filter combinations. If a tab requires many filter conditions, consider breaking it into multiple simpler tabs.
- Test filter results: After creating a tab, review the preview to ensure the filter results match your expectations.
- Document filter logic: If your organization uses complex filters, document the filter logic so other users understand the tab's purpose.
- Review tabs regularly: Periodically review your custom tabs to ensure they remain relevant and useful to your users.
- Use consistent naming conventions: Establish naming conventions for tabs to make them easier to understand and manage.