--- name: account-catalog-settings title: Managing catalog settings description: As the account owner or administrator, you can manage the settings for all catalogs across your account. Management tasks include setting the visibility of the IBM Cloud® catalog and controlling access to products in the public catalog and private catalogs for users in your account. You can also follow the changes that have been made to your private catalogs with audit logs. Changes to your private catalog are associated with your account, products, and catalog. last-updated: 2026-04-16 --- > ## Documentation Index > The table of contents for this documentation set is at https://cloud.ibm.com/docs/account?format=markdown > The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt > Use these files to discover more information as needed. # Managing catalog settings {: #filter-account} As the account owner or administrator, you can manage the settings for all catalogs across your account. Management tasks include setting the visibility of the IBM Cloud® catalog and controlling access to products in the public catalog and private catalogs for users in your account. You can also follow the changes that have been made to your private catalogs with audit logs. Changes to your private catalog are associated with your account, products, and catalog. {: shortdesc} All private catalogs that are in an account inherit filters that are set by the account owner or administrator at the account level. In addition, if the account is a parent account in an IBM Cloud enterprise, the filters apply to all child account groups and accounts. {: tip} ## Before you begin {: #set-before-begin} 1. Verify that you're using a Pay-As-You-Go or Subscription account. See [Viewing your account type](https://cloud.ibm.com/docs/account?topic=account-account_settings&format=markdown#view-acct-type) for more details. 1. Verify that you have the [administrator role on the catalog management service](https://cloud.ibm.com/docs/iam?topic=iam-account-services&interface=ui&format=markdown#catalog-management-account-management). 1. If you want users to have access to products in your account, make sure that you [create a private catalog](https://cloud.ibm.com/docs/account?topic=account-restrict-by-user&interface=ui&format=markdown) before you update the IBM Cloud catalog visibility setting. 1. To view the audit logs, you need to be a manager of the account the catalog is in, or an editor in that account and the catalog. See [Assigning access to account management services](https://cloud.ibm.com/docs/iam?topic=iam-account-services&format=markdown) for more information. ## Updating the visibility of the IBM Cloud catalog by using the console {: #set-public-visibility} {: ui} Users in your account have access to all products in the public catalog by default. If you turn off the visibility of the public IBM Cloud catalog, users can't use the console to create instances of products unless you give them access to a private catalog in your account. To update what products are visible to users, go to **Manage** > **Catalogs** > **Settings > Set the visibility of the IBM Cloud catalog in this account** in the IBM Cloud console. This setting also controls visibility of the IBM® module registry and community registry. For more information, see [Open source offerings](https://cloud.ibm.com/docs/overview?topic=overview-whatis-platform&format=markdown#solutions-open-source). Some products aren't affected by catalog visibility settings. Users can create instances of these products by using an API or the CLI. For more information, see [Known issues and limitations](https://cloud.ibm.com/docs/account?topic=account-known-issues&format=markdown). {: important} ## Managing access to products for all users by using the console {: #set-account-filters} {: ui} You can use filters to manage which products in the public catalog are available to all users in your account. For example, you might want to restrict access to third-party products. Or, you might want users to work with a specific software type. If your account is a parent account in an IBM Cloud enterprise, the filters that you set apply to all child account groups and accounts. For more information, see [Customizing the IBM Cloud catalog for an enterprise](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-catalog-enterprise-restrict&interface=ui&format=markdown). 1. Go to **Manage** > **Catalogs** > **Settings** in the IBM Cloud console. 2. Confirm that the visibility of the public catalog is set to **On**. 3. In the What products are available? section, select **Exclude all products in the IBM Cloud catalog**. 4. Set one or more [filters](#catalog-filters-customize) to customize what products are available by category. 5. (Optional) Add exceptions to the filter rules that you set in the previous step. 6. Use the **Preview** table to confirm your selections, and click **Update**. ## Managing access to products for specific users in the console {: #set-private-filters} {: ui} Set filters at a private catalog level for fine-grained control of which products in the public catalog are available only to the users you choose. 1. Go to **Manage** > **Catalogs**, **Private catalogs** in the IBM Cloud console. 2. Select a catalog from the list to navigate to its details page. The **Products in the IBM Cloud catalog** table that's displayed on the page shows the list of products that are available at the account level. The availability is based on the filters the account owner or administrator set. Account-level filters apply to all the private catalogs in the account. {: tip} 3. Click **Manage filters**. 4. Select to include or exclude all products in the public catalog. 5. Set one or more [filters](#catalog-filters-customize) to customize what products are available by category. 6. (Optional) Add exceptions to the filter rules that you set in the previous step. 7. Click **Update**. 8. Go to the Settings page and turn off the visibility of the public catalog. 9. To give users access to work with the products in the private catalog, assign them the [viewer role on the catalog management service](https://cloud.ibm.com/docs/iam?topic=iam-account-services&interface=ui&format=markdown#catalog-management-account-management). For more detailed examples of how you can leverage filtering at the private catalog level, see [Customizing your private catalogs](https://cloud.ibm.com/docs/account?topic=account-restrict-by-user&format=markdown). ## Updating the visibility of the IBM Cloud catalog by using the CLI {: #set-public-visibility-cli} {: cli} Users in your account have access to all products in the IBM Cloud public catalog by default. You can make products available only to the users you choose by turning off visibility to the IBM Cloud catalog and adding the products to your private catalogs. This setting also controls visibility of the IBM® module registry and community registry. For more information, see [Open source offerings](https://cloud.ibm.com/docs/overview?topic=overview-whatis-platform&format=markdown#solutions-open-source). Use the following command to turn off visibility of the public catalog to all users in your account. ```bash ibmcloud catalog filter hide-ibm-public-catalog ``` {: codeblock} ## Managing access to products for all users by using the CLI {: #set-account-filters-cli} {: cli} You can use filters to manage which products in the public catalog are available to all users in your account. For example, you might want to restrict access to third-party products. Or, you might want users to work with a specific software type. If your account is a parent account in an IBM Cloud enterprise, the filters that you set apply to all child account groups and accounts. For more information, see [Customizing the IBM Cloud catalog for an enterprise](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-catalog-enterprise-restrict&interface=ui&format=markdown). {: tip} 1. Create a new filter. ```bash ibmcloud catalog filter create [--catalog CATALOG] [--category CATEGORY] [--compliance COMPLIANCE] [--deployment-target TARGET] [--exclude-list LIST] [--include-all ALL] [--include-list LIST] [--offering-format FORMAT] [--pricing-plan PLAN] [--provider PROVIDER] [--release RELEASE] [--type TYPE] ``` {: codeblock} When the `--catalog CATALOG` command is not specified, the filter is created at the account level. 1. Target an account group by specifying the command option `--account-group ACCOUNT GROUP`. 1. Update the filter to include or exclude a particular product or products. See the [Catalog management CLI](https://cloud.ibm.com/docs/cli?topic=cli-manage-catalogs-plugin&format=markdown#create-filter) guidance for command options or run the `ibmcloud catalog filter options` command to retrieve the filter options for each filter category. ## Managing access to products for specific users by using the CLI {: #set-private-filters-cli} {: cli} Set filters at a private catalog level for fine-grained control of which products in the public catalog are available only to the users you choose. 1. Create a new filter. ```bash ibmcloud catalog filter create [--catalog CATALOG] [--category CATEGORY] [--compliance COMPLIANCE] [--deployment-target TARGET] [--exclude-list LIST] [--include-all ALL] [--include-list LIST] [--offering-format FORMAT] [--pricing-plan PLAN] [--provider PROVIDER] [--release RELEASE] [--type TYPE] ``` {: codeblock} Make sure to specify the `--catalog CATALOG` command option. When `--catalog CATALOG` is not specified, the filter is created at the account level. 1. Target an account group by specifying the command option `--account-group ACCOUNT GROUP`. 1. Update the filter to include or exclude a particular product or products. See the [Catalog management CLI](https://cloud.ibm.com/docs/cli?topic=cli-manage-catalogs-plugin&format=markdown#create-filter) guidance for command options or run the `ibmcloud catalog filter options` command to retrieve the filter options for each filter category. ## Updating the visibility of the IBM Cloud catalog by using the API {: #set-public-visibility-api} {: api} Users in your account have access to all products in the IBM Cloud public catalog by default. You can make products available only to the users you choose by turning off visibility to the IBM Cloud catalog and adding the products to your private catalogs. This setting also controls visibility of the IBM® module registry and community registry. For more information, see [Open source offerings](https://cloud.ibm.com/docs/overview?topic=overview-whatis-platform&format=markdown#solutions-open-source). Use the following command to turn off visibility of the public catalog to all users in your account. ```bash curl -X "PUT" "https://cm.globalcatalog.cloud.ibm.com/api/v1-beta/catalogaccount" -H "accept: */*" -H "Authorization: {iam-bearer-token}" -d '{"id":"string","hide_IBM_cloud_catalog":true,"account_filters":{"include_all":true,"category_filters":{"additionalProp1":{"include":true,"filter":{"filter_terms":["string"]}},"additionalProp2":{"include":true,"filter":{"filter_terms":["string"]}},"additionalProp3":{"include":true,"filter":{"filter_terms":["string"]}}},"id_filters":{"include":{"filter_terms":["string"]},"exclude":{"filter_terms":["string"]}}}}' ``` {: codeblock} Make sure the `hide_IBM_cloud_catalog` field has a Boolean value of `true` to hide the public catalog in this account. Alternatively, you can give the `include_all` field a Boolean value of `false` for each `account_filters` object to exclude all of the public catalog. See the [Catalog Management API](https://cloud.ibm.com/apidocs/resource-catalog/private-catalog?code=curl#update-catalog-account){: external} for more information. ## Managing access to products for all users by using the API {: #set-account-filters-api} {: api} You can use filters to manage which products in the public catalog are available to all users in your account. For example, you might want to restrict access to third-party products. Or, you might want users to work with a specific software type. If your account is a parent account in an IBM Cloud enterprise, the filters that you set apply to all child account groups and accounts. For more information, see [Customizing the IBM Cloud catalog for an enterprise](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-catalog-enterprise-restrict&interface=ui&format=markdown). {: tip} ```bash curl -X "PUT" "https://cm.globalcatalog.cloud.ibm.com/api/v1-beta/catalogaccount" -H "accept: */*" -H "Authorization: {iam-bearer-token}" -d '{"id":"string","hide_IBM_cloud_catalog":true,"account_filters":{"include_all":true,"category_filters":{"additionalProp1":{"include":true,"filter":{"filter_terms":["string"]}},"additionalProp2":{"include":true,"filter":{"filter_terms":["string"]}},"additionalProp3":{"include":true,"filter":{"filter_terms":["string"]}}},"id_filters":{"include":{"filter_terms":["string"]},"exclude":{"filter_terms":["string"]}}}}' ``` {: codeblock} The options for `{accountFilters}` are: `include_all`, `category_filters`, and `id_filters`. See the [Catalog Management API](https://cloud.ibm.com/apidocs/resource-catalog/private-catalog?code=curl#update-catalog-account){: external} for more information. ## Managing access to products for specific users by using the API {: #set-private-filters-api} {: api} Set filters at a private catalog level for fine-grained control of which products in the public catalog are available only to the users you choose. The following example applies the filter `id_filters` where `AdvancedMobileAccess-d6aece47-d840-45b0-8ab9-ad15354deeea` is a product ID. ```bash curl -X 'PUT' \ 'https://cm.globalcatalog.cloud.ibm.com/api/v1-beta/catalogs/' -H 'accept: application/json' \ -H 'Content-Type: application/json' \ -H "Authorization: ${IC_IAM_TOKEN}" \ -d '{"label": "testcurlcatalog4", "short_description": "testing creating a catalog through curl", "catalog_filters": { "include_all": false, "id_filters": { "include": { "filter_terms": [ "AdvancedMobileAccess-d6aece47-d840-45b0-8ab9-ad15354deeea" ] } } }}' ``` {: codeblock} See the [Catalog Management API](https://cloud.ibm.com/apidocs/resource-catalog/private-catalog?code=curl#replace-catalog){: external} for more information. ## Catalog filters {: #catalog-filters-customize} The following table lists the filters that you can use to customize which products in the public catalog are available to users in your account. | Option | Description | |------------------|-------| | AI / Machine Learning | Products that enable systems to learn from data rather than through explicit programming. | | Analytics | Products that facilitate the analysis of data, typically large sets of business data, by the use of mathematics, statistics, and other means. | | Blockchain | Products that facilitate the process of recording transactions and tracking assets in a business network. | | Compute | Infrastructure resources that serve as the basis for building apps in the cloud. | | Containers | A standard unit of software that packages up code and all its dependencies so the app runs quickly and reliably from one computing environment to another. | | Databases | Products that provide some form of access to a database without the need for setting up physical hardware, installing software, or configuring for performance. | | Developer tools | Products that support developing, testing, and debugging software. | | Enterprise applications | Bundle of compatible products that deliver enterprise-grade app solutions for information sharing, automation, and agility. | | Integration | Products that facilitate the connection of data, apps, APIs, and devices across an organization to be more efficient, productive, and agile. | | Internet of Things | Products that support receiving and transferring data over wireless networks without human intervention. | | Logging and monitoring | Products that support receiving and transferring data over wireless networks without human intervention. | | Mobile | Products with specific or special utility for users creatings things to be used on mobile devices. | | Networking | Products that support or augment the linking of computers so they can operate interactively. | | Security | Products that provide the protection of stored data from theft, leakage, and deletion. | | Storage | Products that support data to be created, read, updated, and deleted. | {: caption="Options for filtering by category" caption-side="top"} {: #category-custom} {: tab-title="Category"} {: tab-group="customcatalogfilters"} {: class="simple-tab-table"} {: summary="Use the buttons before the table to change the context of the table. The column headers identify the options for fitering based on filter type."} | Option | Description | |--------------|-------| | EU Supported | Support for the service is provided by IBM Cloud support team members that are located in the European Union (EU) region. | | Financial Services Validated | Services are designated as Financial Services Validated when the IBM Cloud service or SaaS, or independent software vendor (ISV) offering, evidences compliance with the IBM Cloud Framework for Financial Services. | | HIPAA Enabled | The service is designated as HIPAA ready, meaning processing, storing, and handling Protected Health Information (PHI) in the service is supported. | | IAM-enabled | The service is enabled to use IBM Cloud Identity and Access Management (IAM) for access control. Access policies are used to assign users and service IDs access to specific resources in an account.| | Service Endpoint Supported | The service can be connected to over the IBM Cloud private network instead of the public network. Connecting directly to service endpoints doesn't require internet access, providing increased security. | {: caption="Options for filtering by compliance" caption-side="top"} {: #compliance-custom} {: tab-title="Compliance"} {: tab-group="customcatalogfilters"} {: class="simple-tab-table"} {: summary="Use the buttons before the table to change the context of the table. The column headers identify the options for fitering based on filter type."} | Option | Description | |--------------|-------| | Cloud Paks | A cloud solution that integrates a container platform, containerized IBM middleware and open source components, and common software services for development and management. | | Helm charts | A format for packaging a collection of files that describe specific configurations of infrastructure in the form of code. | | Operators | A method of packaging and deploying a Kubernetes-native application. | | OVA Images | Open Virtual Appliance that contains a compressed installable version of a virtual machine. | | Server Images | A template that is used to create instances of virtual servers. | | Terraform | Infrastructure as code to deploy your application. | {: caption="Options for filtering by delivery method" caption-side="top"} {: #software-custom} {: tab-title="Delivery method"} {: tab-group="customcatalogfilters"} {: class="simple-tab-table"} {: summary="Use the buttons before the table to change the context of the table. The column headers identify the options for fitering based on filter type."} | Option | Description | |--------------|-------| | IBM Kubernetes Service | Used to create a Kubernetes cluster of compute hosts to deploy and manage containerized apps on IBM Cloud. | | IBM Cloud Schematics | Used for infrastructure as code automation by using terraform templates. | | Power Virtual Server | Used to create a Power server that is distinct from the IBM Cloud servers with separate networks and direct-attached storage. The internal networks are fenced but offer connectivity options to IBM Cloud infrastructure or on-premises environments. | | Red Hat OpenShift | Used to create a Red Hat OpenShift on IBM Cloud cluster of compute hosts to deploy and manage containerized apps on IBM Cloud. | | VMware vCenter Server | Provides deployment and management of VMware virtualized environments. | | Virtual Private Cloud | Deploy and manage your server images on virtual private cloud as your infrastructure target. | {: caption="Options for filtering by deployment target" caption-side="top"} {: #swdeploymenttargetfilters} {: tab-title="Deployment target"} {: tab-group="customcatalogfilters"} {: class="simple-tab-table"} {: summary="Use the buttons before the table to change the context of the table. The column headers identify the options for fitering based on filter type."} | Option | Description | |--------------|-------| | Free | The service includes monthly free allowances for only Pay-As-You-Go or Subscription accounts. | | Lite | The pricing plan for the service is structured as a free quota. The quota might operate for a specific time period, for example, a month or on a one-off usage basis. | {: caption="Options for filtering by pricing plan" caption-side="top"} {: #pricingplan-svc} {: tab-title="Pricing plan"} {: tab-group="customcatalogfilters"} {: class="simple-tab-table"} {: summary="Use the buttons before the table to change the context of the table. The column headers identify the options for fitering based on filter type."} | Option | Description | |--------------|-------| | Beta | The product is available for evaluation and testing purposes. Beta products are not intended for production use. | | Deprecated | The product is supported but no longer recommended and that might become obsolete. | {: caption="Options for filtering by release" caption-side="top"} {: #release-custom} {: tab-title="Release"} {: tab-group="customcatalogfilters"} {: class="simple-tab-table"} {: summary="Use the buttons before the table to change the context of the table. The column headers identify the options for fitering based on filter type."} | Option | Description | |--------------|-------| | HPC | Products that enable High Performance Computing (HPC) workloads on IBM Cloud. For more information, see [High-performance computing on IBM Cloud](https://www.ibm.com/solutions/high-performance-computing){: external} | | SAP Certified | An infrastructure service that is certified by SAP to run production SAP workloads. For more information, see [IBM Cloud® for SAP](https://cloud.ibm.com/docs/sap?format=markdown).| | Satellite Enabled | A service that is enabled for use with IBM Cloud Satellite. You can run apps consistently across on-premises, edge computing, and public cloud environments. For more information, see [IBM Cloud Satellite](https://www.ibm.com/products/satellite){: external}. | | Quantum Technologies | A service that is compatible with quantum technologies. For more information, see [IBM Quantum services](http://cloud.ibm.com/quantum){: external}. | {: caption="Options for filtering by runtime environment" caption-side="top"} {: #works-with-custom} {: tab-title="Works with"} {: tab-group="customcatalogfilters"} {: class="simple-tab-table"} {: summary="Use the buttons before the table to change the context of the table. The column headers identify the options for fitering based on filter type."} | Option | Description | |--------------|-------| | IBM supported | Products that are supported by IBM Cloud. | | Third party supported | Products that are provided by individual service entities. | | Community supported | Products that are provided by open source communities. | {: caption="Options for filtering by support type" caption-side="top"} {: #support-type-custom} {: tab-title="Support"} {: tab-group="customcatalogfilters"} {: class="simple-tab-table"} {: summary="Use the buttons before the table to change the context of the table. The column headers identify the options for fitering based on filter type."} You can also scope your view of the catalog by using the **Provider** filter to browse by individual providers, and the **Location** filter to view products available in specific regions. {: tip} ## Viewing changes by using the console {: #audit-logs-table} {: ui} 1. In the IBM Cloud® console, go to **Manage** > **Catalogs** from the console menu bar. 2. Select **Audit logs**. 3. Filter for the scope you want to see in the table. Each event in the audit logs table by default identifies each change with the email of the user that made the change, the type of change, a description of the change, and the date that the change was made. ## Viewing changes by using the CLI {: #audit-logs-table-cli} {: cli} This action can be done only through the console, API, or SDKs. To see the steps, switch to the UI or API instructions. ## Viewing changes by using the API {: #audit-logs-table-api} {: api} You can view changes made to your private catalogs by calling the [Catalog Management API](https://cloud.ibm.com/apidocs/resource-catalog/private-catalog#get-catalog-audit) as shown in the following sample request. ```bash curl -X "GET" \ "https://cm.globalcatalog.cloud.ibm.com/api/v1-beta/catalogs/{catalog-id}/audit" -H "accept: application/json" -H "Authorization: {iam-bearer-token}" ``` {: codeblock} Each event in the audit logs table by default identifies each change with the email of the user that made the change, the type of change, a description of the change, and the date that the change was made.