---
sourceDocument: Australia Customer Success Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/acct-lifecycle-events

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Customer Success Management

ft:clusterId :

    - actle

bundleId :

    - actle

workflow :

    - Customer and Industry


---

# Product use case catalog

# Product use case catalog {#ariaid-title1}

Release version: Australia  
Updated July 1, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Define how a product solves a problem by creating use cases in the product use case catalog. Document
process flow, ownership, complexity, audience, and industry context, then map use cases to product models.

## Product use case catalog overview

The product use case catalog provides a structured, reusable way to define how a product addresses customer issues. Without a shared use case catalog, each team builds its own records
in inconsistent formats, resulting in duplicated data, inconsistent lifecycle management, and no cross-product adoption insight.{#account-lifecycle-product-use-case__account-lifecycle-product-use-case-overview-1}

The product use case catalog includes a supported use case catalog that product teams maintain. Supported use cases are associated with product models to show which products support
each use case. This enables customer success teams to reference the catalog when documenting customer-specific implementations.{#account-lifecycle-product-use-case__account-lifecycle-product-use-case-overview-2}  
Note:  
This feature requires the Product Capability Core plugin (com.sn_prod_cap_core). The Supported use case table is available when this plugin is installed.

## How supported use cases work

The Product Use Case catalog contains supported use cases that define the standard ways a product solves customer problems. Customer-facing teams reference these supported use cases when documenting customer use cases in the Customer
Discovery Hub. Each customer use case is linked to a business need and aligned to one or more supported use cases using an alignment value: default (the product's standard approach), extended (a supported variation), or custom (a
customer-specific implementation).

Use cases are associated with one or more product models, enabling traceability between use cases and product solutions. A use case can be associated with an entire product or with a specific capability within that product. These
associations can be edited only while the use case is in Draft state.

The Industry and Audience type fields define which customer segments and verticals the use case targets. This helps customer success teams identify the most relevant use cases for a given customer context. Records
follow a managed publication lifecycle (Draft, Published, Retired, or Cancelled) controlled by UI actions.

## Relationship with Customer Discovery Hub

The Customer Discovery Hub depends on the product use case catalog. When customer success teams create customer use cases, they specify an alignment to supported use cases from this catalog.
This alignment determines whether and how many Supported Use Cases must be linked.{#account-lifecycle-product-use-case__account-lifecycle-product-use-case-cdh-1}

For more information on customer use cases and how they align to supported use cases, see [Customer Discovery Hub](https://servicenow-prod.fluidtopics.net/jegUYH8jHTFST8ZJ_TPvpg "Use the Customer Discovery Hub to capture customer business context during pre-sales and carry that context forward to customer success teams at the post-sale handoff.").{#account-lifecycle-product-use-case__account-lifecycle-product-use-case-cdh-2}
**Related reference**   

* [Customer Discovery Hub tables](https://servicenow-prod.fluidtopics.net/RYfY9zOBBayjL_OGO3uTaQ "The Customer Discovery Hub includes four tables that capture customer business context: customer business need, customer business challenge, customer business expectation, and customer use case.")
* [Supported use case table](https://servicenow-prod.fluidtopics.net/b9wCCAZY0xEv00oB3CxZRA "The supported use case table (sn_prod_cap_core_sup_use_case) is the default implementation of the use case catalog. It extends the base use case table and adds classifies the industry verticals and business model segments relevant to the use case.")