> ## Documentation Index > Fetch the complete documentation index at: https://docs.incident.io/llms.txt > Use this file to discover all available pages before exploring further. # Using the Catalog ## Introducing Catalog The Catalog is a connected map of “everything” that exists in your organization that you can easily navigate and is available across features like Workflows, Insights, and Triggers to level up your incident response. ## Getting started with Catalog The best place to get started is by following [this hands-on lab session on YouTube](https://www.youtube.com/watch?v=aW0AY3jhdJE). ## Integrating with an existing Service Catalog Already using a Service Catalog? No problem! We support a number of [Integrations](/catalog/backstage). ## What can I do with Catalog? Many things! Including, but not limited to: * [Populating Custom Fields with Catalog data](/catalog/catalog-setup) * [Automatic Custom Fields](/catalog/catalog-setup) * [Using the Catalog in Workflows](/catalog/catalog-setup) * [Powering your Status Page Sub-pages](/catalog/catalog-setup) ### Populating Custom Fields with Catalog data Fed up with manually maintaining options for custom fields? When configuring [custom fields](/incidents/custom-fields), select "From a catalog type" as an option for how the field should be managed. This means that any updates made to a Catalog type will be updated in this custom field. If you want to migrate an existing custom field to be managed from a Catalog type, go to the existing custom field that you would like to migrate and follow the migration wizard. ### Automatic Custom Fields Want to update the value of a custom field based on the value of another custom field? For example, when selecting the Affected Service, using the Catalog you could derive the Affected Team without having an Incident Responder select anything. When creating a custom field, select Automated, and then Add an expression. Then, use the Expression Builder to navigate through your Catalog to automatically derive a custom field based on the value of another custom field. ### Using the Catalog in Workflows Once you've set up custom fields for the relevant Catalog types, you can use those custom fields in [Workflows](https://app.incident.io/~/workflows). For example: * Escalate incidents to the right on-call engineers when certain business functionality is impacted. * Invite Customer Success Managers to incidents when their customers are mentioned. * Notify the executive team when an aggregate amount of revenue across impacted customers crosses a threshold. ### Powering your Status Page sub-pages Sub-pages are part of our status page offering, and allow you to create a page that is specific to different services, systems, products, or regions. In short, if you operate across multiple countries (UK, US, France), you can have one status page per region. Catalog supercharges sub-pages by allowing you to associate components/services/systems with regions. For instance, you can say that the API is only used in the UK and France, whilst the Website is used in all regions. This means when you author an update, we can automatically route that update to the relevant sub-pages. To find out more about setting up sub-pages, visit [this helpful article](/status-pages/sub-page-setup). ### Visualize with Catalog Graph Use the Catalog Graph to visualize how different catalog entries connect to each other. You can build up a graph from any catalog entry, and share the URL so colleagues see the same view.