Skip to main content
🔍

DAM Audit Webinar

Learn how to clean, organize, and optimize your DAM portal.
Question

UCV showing only public assets

  • February 6, 2026
  • 2 replies
  • 8 views
C

Hi 
Is there a way to use UCV to filter only public assets without making them as defaultSearchTerm “isPublic:1”

The idea is “I do not want the end user to remove that isPublic:1 and see the not public assets yet”
As I know I can’t use Predefined Metaproperty Ids as Public is not part of those metaproperties.

I see we can filter on isLimitedUse but none on isPublic

type AssetFilterJson = {	predefinedAssetType?: AssetType[]; //predefined asset types	collectionId?: string; //predefined collection id	predefinedMetapropertiesOptions?: string[]; //predefined metaproperty IDs	searchTerm?: string; //predefined search term	predefinedTagNames?: string[]; //predefined tags	isLimitedUse?: boolean; //whether or not this asset is marked as Limited Use	showToolbar?: boolean; //show toolbar for predefined filters (false by default)};Thanks in advance.

    2 replies

    Ryanne Perry
    Community Manager
    Forum|alt.badge.img+1
    • Ryanne Perry
    • Community Manager
    • February 9, 2026

    Hi ​@chaabni, yes you can use the assetFilter attribute in UCV to enforce that only public assets are shown and this filter cannot be removed by users like a defaultSearchTerm can.

    Here's how it works:

    When you configure UCV, you can pass an assetFilter object that sets structural constraints. For example:

    BynderUniversalCompactView.open({ clientId: '<YOUR_CLIENT_ID>', portal: 'https://example.bynder.com', assetFilter: { isPublic: true }, toolbar: false // Optional: hides filters so users can't change it });


    Key differences from defaultSearchTerm:

    • assetFilter is a structural filter that users can't simply edit or delete
    • defaultSearchTerm is just a search string that appears in the search box and can be modified
    • Setting toolbar: false prevents users from adding or changing filters entirely (strict enforcement)
    • Setting toolbar: true allows users to see the filter UI, but they'd be starting with your preset filter

    This approach is documented in the UCV configuration and was specifically designed for cases like yours where you need to guarantee only certain assets (like public ones) can be selected. [1]

    If you need to combine multiple filters (like public SVGs only), you can do:

    assetFilter: { isPublic: true, extensions_in: ['svg', 'SVG'] }

    Ryanne, Community Manager ☀️
    C
    • chaabni
    • Author
    • February 9, 2026

    Hi ​@chaabni, yes you can use the assetFilter attribute in UCV to enforce that only public assets are shown and this filter cannot be removed by users like a defaultSearchTerm can.

    Here's how it works:

    When you configure UCV, you can pass an assetFilter object that sets structural constraints. For example:

    BynderUniversalCompactView.open({ clientId: '<YOUR_CLIENT_ID>', portal: 'https://example.bynder.com', assetFilter: { isPublic: true }, toolbar: false // Optional: hides filters so users can't change it });


    Key differences from defaultSearchTerm:

    • assetFilter is a structural filter that users can't simply edit or delete
    • defaultSearchTerm is just a search string that appears in the search box and can be modified
    • Setting toolbar: false prevents users from adding or changing filters entirely (strict enforcement)
    • Setting toolbar: true allows users to see the filter UI, but they'd be starting with your preset filter

    This approach is documented in the UCV configuration and was specifically designed for cases like yours where you need to guarantee only certain assets (like public ones) can be selected. [1]

    If you need to combine multiple filters (like public SVGs only), you can do:

    assetFilter: { isPublic: true, extensions_in: ['svg', 'SVG'] }

    Hi ​@Ryanne Perry 

    Thank you for answering 

    sadly the current AssetFilterJSON take those elements
     [predefinedAssetType, collectionId, predefinedMetapropertiesOptions, searchTerm, tagNames, isLimitedUse]
    even if you put isPublic: true it won’t filter

    type AssetFilterJson = {	predefinedAssetType?: AssetType[]; //predefined asset types	collectionId?: string; //predefined collection id	predefinedMetapropertiesOptions?: string[]; //predefined metaproperty IDs	searchTerm?: string; //predefined search term	predefinedTagNames?: string[]; //predefined tags	isLimitedUse?: boolean; //whether or not this asset is marked as Limited Use	showToolbar?: boolean; //show toolbar for predefined filters (false by default)};the toolbar I used that case when I can handle custom or predefined metapropery (isPublic and isLimitedUse are not part of metaproperties)@bynder/compact-view - npm
    Bynder Community TermsCookie settingsAccessibility statement