> ## 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.

# Creating an internal status page

Get an internal status page set up in three steps:

1. **Choose a name**

<img src="https://mintcdn.com/incidentio-18bb4170/I3iKG7Pm9YQiOUVJ/images/help-centre/creating-an-internal-status-page/screenshot-1.png?fit=max&auto=format&n=I3iKG7Pm9YQiOUVJ&q=85&s=33ff138d12c7273ca7ad333825a43f94" alt="" width="1626" height="686" data-path="images/help-centre/creating-an-internal-status-page/screenshot-1.png" />

This name will be the page heading and the default bookmark name if people choose to bookmark the page in their browser or in Slack channels.

2. **Choose your components**

To keep things simple for responders, the components shown on the status page are based on a custom field. If you have a field like ‘Impacted Products’ or ‘Affected Services’, that’s probably a good place to start.

*Note: You can only use multi-select custom fields to power your components.*

<img src="https://mintcdn.com/incidentio-18bb4170/I3iKG7Pm9YQiOUVJ/images/help-centre/creating-an-internal-status-page/screenshot-2.png?fit=max&auto=format&n=I3iKG7Pm9YQiOUVJ&q=85&s=79ad87b606bf1379ca16c2fea58e936e" alt="" width="1626" height="1310" data-path="images/help-centre/creating-an-internal-status-page/screenshot-2.png" />

If you want to simplify which components are shown on your internal page compared to the full list of options in the custom field, you can use an [Automated Custom Field](/catalog/catalog-setup) to combine options.

For example, if you have a list of ‘services’ and ‘features’ in your Catalog, you can add an attribute that lists which features are powered by each service:

<img src="https://mintcdn.com/incidentio-18bb4170/I3iKG7Pm9YQiOUVJ/images/help-centre/creating-an-internal-status-page/screenshot-3.png?fit=max&auto=format&n=I3iKG7Pm9YQiOUVJ&q=85&s=161218537472e72c01e23405aac9edff" alt="" width="1650" height="1710" data-path="images/help-centre/creating-an-internal-status-page/screenshot-3.png" />

You can now create a ‘Features’ custom field that is set automatically when the ‘Services’ custom field is set, translating from the technical services to the product features impacted:

<img src="https://mintcdn.com/incidentio-18bb4170/I3iKG7Pm9YQiOUVJ/images/help-centre/creating-an-internal-status-page/screenshot-4.png?fit=max&auto=format&n=I3iKG7Pm9YQiOUVJ&q=85&s=8a44e0cfbc37d22d2dc8f3bdfed95770" alt="" width="1628" height="1008" data-path="images/help-centre/creating-an-internal-status-page/screenshot-4.png" />

Using the ‘Features’ custom field to power your internal status page keeps the complexity of how different services impact your product in the background and lets your customer success team understand what customers will be seeing.

### Component Ordering

If the custom field used on the internal status page is backed by catalog type as in the example above, you have 2 options for the ordering of components:

* Alphabetically
* Ranked

more info in this [article](/status-pages/component-ordering).

If not using a catalog-backed custom field, the ordering will be shown as it is set in the custom field.

3. **Customize your branding**

Choose between light and dark themes and add your logo and you’re ready to go!

## → What’s next?

By default, live incidents will be automatically added to your internal status page if they affect any of the components listed on your page. You can configure this under ' *Settings > Automation* '.

You can also add additional context to your internal status page by showing additional custom fields. Configure this under ‘Basic settings’ in the Settings tab.
